Exim : retry time not reached for any host after a long failure period

The issue is because of the corrupted exim db files.

Goto /var/spool/exim/db and delete files: retry , retry.lockfile , wait-remote_smtp, wait-remote_smtp.lockfile

/etc/init.d/exim restart


25 thoughts on “Exim : retry time not reached for any host after a long failure period

  1. Peter Panic says:

    Thanks so much. That was the problem and the only solution that really helped. The Exim FAQ isn’t of any help and many forums are neither.


  2. Enas says:

    when i restart , the lockfile returns again!!!!!!!!!!!!!!!!!!!!

    i need also to know , is the problem from sender side or receiver????


  3. zebulon says:

    Thanks a lot, it’s solved my problem.

    after upgrade from lenny to squeeze I don’t receive emails on my company but for others it’s


  4. Rennix says:

    There’s a more elegant way:

    The problem is usually NOT DB corruption! Just simply force a mail to the failing domain into the mailqueue:

    “exim -odq recipient@faileddomain.com
    .” (Don’t forget that last dot)

    Find out the message id:
    “exim -bpu”

    Force the delivery:
    exim -M somemessageid

    After a successful delivery exim will reset it’s retry database for that specific mailhost. No need to delete the entire DB or restart the MTA.


  5. Johne723 says:

    whoah this blog is excellent i really like reading your articles. Stay up the good work! You already know, many persons are looking around for this info, you could help them greatly. ekakedkgaace


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s