Author: Sander Smeenk Date: To: exim-users Subject: [exim] Retry time not reached for any host after a long failure
period
Hi,
The internet is full of crap about a delivery failure message returned
by Exim: "retry time not reached for any host after a long failure period".
Every post i can find suggests my retry databases are corrupt, but i am
certain they are not. Ofcourse, removing the retry database would
"""solve""" the issue with the bounce message being sent, but it would
return sooner or later as the remote host is still experiencing problems.
This bit is clear to me. Remote host is not coöperative, Exim remembers
and wont waste resources for some configurable timeperiod.
However, i can't seem to explain to my cow-orkers why it is our MTA
*immediately* rejects a message to a destination that has had issues for
a longer time. They would expect Exim to queue the message and retry
before returning it to the sender as failed. Actually, i do too.
Any hints on this subject?
Could we devise a clearer bounce message for this situation?
-Sander.
-- | There's no such thing as 'bad weather', there's only inapproriate clothing.
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
