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

About these ads
About

anees

Posted in Issues, Mail
25 comments on “Exim : retry time not reached for any host after a long failure period
  1. gjsmith66 says:

    Great Help, thanks!

    Like

  2. 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.

    Like

  3. Stuart says:

    Yesss : ) legend!

    Like

  4. Tom says:

    After you’ve done this you force all the mail in the queue to resend with ‘exim4 -qf’

    Like

  5. Mike says:

    Thank you!

    Like

  6. Ashok says:

    Thank you..

    Like

  7. Sunny says:

    It’s works! Thanks!

    Like

  8. Enas says:

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

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

    Like

  9. lameritos says:

    Помогло, спасибо!
    It’s works! Thanks!

    Like

  10. Ryan says:

    Fixed my problem…thanks!!!

    Like

  11. It’s works! Thanks!

    Like

  12. Phillip says:

    Thanks!!

    Like

  13. 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

    Like

  14. asiams says:

    It works like charm!!

    Like

  15. We did not get any mails from domain to domain on cpanel, I am able to receive mail from outside

    Like

  16. 송보근 says:

    감사합니다!
    Thanks!!!!!!!

    Like

  17. [...] Украл тут [...]

    Like

  18. It’s going to be finish of mine day, however before finish I am reading this great article to improve my knowledge.

    Like

  19. Its like you read my mind! You seem to know so much about this,
    like you wrote the book in it or something. I think that you could
    do with a few pics to drive the message home a bit, but instead of that,
    this is wonderful blog. A great read. I will certainly be
    back.

    Like

  20. Great information. Lucky me I ran across your blog by chance (stumbleupon).
    I’ve book-marked it for later!

    Like

  21. Master says:

    great thanks, it helped.

    Like

  22. 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
    Testmail.
    .” (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.

    Like

  23. 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

    Like

  24. Day every, Facebook scans over a trillion hyperlinks.

    Like

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

Blog Stats
  • 118,277 hits
Follow

Get every new post delivered to your Inbox.

Join 209 other followers

%d bloggers like this: