On Fri, 29 Apr 2005, at 16:08, Philip Hazel typed:
> On Fri, 29 Apr 2005, Mark Rigby-Jones wrote:
>> # Domain Error Retries
>> # ------ ----- -------
>> * * senders=: G,4h,5m,2
>> cdb*@;/etc/mail/retry/dialup.cdb * F,28d,7d
>> cdb*@;/etc/mail/retry/server.cdb * F,2h,15m; F,16h,1h; F,14d,8h
>> cdb*@;/etc/mail/retry/local.cdb * F,2h,15m; F,16h,1h; F,14d,8h
>> * * F,2h,15m; F,16h,1h; F,4d,8h
>
> Given that set of retry rules, I am completely baffled... wait ... I
> notice that 10 hours and 40 minutes is 640 minutes. That amount of retry
> time can be the result of 5 minutes multiplied by 2 several times, which
> is the algorithm in your first retry rule. Did the message have an empty
> sender? But that rule should have timed out after 4 hours...
The particular message I was looking at didn't have an empty sender, but by
that point, the host was already marked as past its final cutoff time in
the retry hints file.
Could, then, a message with an empty sender failing after 4 hours cause the
host to get marked as 'past final cutoff' in the hints db even though other
messages have a final cutoff time of four days? That would certainly
explain pretty much everything I'm seeing, and I have a sneaking suspicion
that the first time I saw this behaviour (on a different server) was not
long after I intorduced the "senders=:" retry rule.
Hmmm. I think I'll comment out that rule for the time being and see if it
makes any difference.
mrj
--
Mark Rigby-Jones, Operations Manager @ Community Internet plc
Windsor House, 12 High Street, Kidlington, Oxford OX5 2PJ, UK
Tel: +44-1865-856000 (Direct: +44-1865-856009) Fax: +44-1865-856001
mrj@??? <*> http://www.community.net.uk/~mrj
