Exim db corrupt with a few entries?

[sahostking]

Hi guys,

Today we had a client that receiving the following error when sending to a particular email address:

Bounced Message "retry time not reached for any host after a long failure period"

I would've thought it may be ISP being sent to was the issue. However dug a bit deeper before responding to client and found that doing this fixed the issue:

cd /var/spool/exim/db
rm -f retry retry.lockfile
rm -f wait-remote_smtp wait-remote_smtp.lockfile
service exim restart

Any ideas if I should automate this as a cronjob and if it's a good idea or not?

 

[ThinIce]

The root cause of an entry appearing to get 'stuck' in the exim database like this is generally a failed dns lookup. As such you might like to check your resolvers - generally manually clearing the lock files / exim db in this manner should rarely be necessary

 

[cPanelMichael]

Hello

It's not a good idea to implement a cron job with those commands. It's possible the message failed due to a network issue, but it should be investigated more if you notice this start to happen regularly.

Thank you.

 

[sahostking]

Thanks guys.

Only happened once in 3 years of this server being live. So probably not an issue. Thanks for the help