Quoting Sander Smeenk (ssmeenk@???):
> There's one retry-rule in my config:
> * * F,4h,5m; F,16h,30m; F,7d,3h
> With this retry rule, I would expect to see no messages older than 7
> days in my queue. Can anyone explain why this message is still on queue?
> 13d 4.7K 1IGNmg-00007X-Ia <>
> jr_sandre@???
As it turns out, these messages eventually *do* leave the queue. But i
still don't understand why they stay on queue for about twice the time
specified by the retry rules.
F.e. with a new message on the queue:
| 11d 4.7K 1IJADT-0002Ak-N1 <>
| jr.f15@???
Doing this:
| % exim4 -v -v -M 1IJADT-0002Ak-N1
Results in:
| delivering 1IJADT-0002Ak-N1
| Connecting to mx.bol.com.br [200.221.29.128]:25 from 10.0.25.1 ... connected
| LOG: MAIN
| Remote host mx.bol.com.br [200.221.29.128] closed connection in
| response to initial connection
| LOG: MAIN
| == jr.f15@??? R=dnslookup T=remote_smtp defer (-18): Remote
| host mx.bol.com.br [200.221.29.128] closed connection in response to
| initial connection
| LOG: MAIN
| ** jr.f15@???: retry timeout exceeded
| LOG: MAIN
| jr.f15@???: error ignored
| LOG: MAIN
| Completed
And the message is gone.
I'd really like to know a way to make these messages disappear at the
specified maximum time on queue, instead of what seems to be twice as long.
Any hints?
Thanks,
-Sndr.
--
| If Barbie's so popular, why do you have to buy all her friends?
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
