On Sat, 22 Jun 2002, Adam Henry wrote:
> Gettings the "defer (-44): retry time not reached for any host" error
> in my logs since about 10pm last night. 10 hours after the first
> log message, mail is finally delivered in one surge. Am I wrong to
> think that the retry rules are in charge of how frequently mail in the
> queue due to this error is sent out again?
>
> Here is what I have as my retry rule:
> > * * F,2h,15m; G,16h,2h,1.5; F,4d,8h
>
> So the retry rule error I get every half an hour is due to the way I
> run exim: '/usr/sbin/exim -bd -q30m'. When the first message came in
> at 10pm last night, "Exim computed the earliest time at which to try
> again" (A0520). This time should have been 15 minutes later, correct?
Correct.
> But for ten hours there is indication that the mail never reached its
> retry time. I am confident that the destination host wasn't down for
> more than 5 minutes.
On the face of it, that is then very mysterious. Were there any previous
failures for this host? And, which release of Exim are you using?
> What configuration parameters have a hand in deciding how Exim
> computes the earliest time to try to send the mail again?
It is just the retry rules.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
