Re: [exim] Potential logic error in retry handling for IPv4+…

* Philip Hazel:

> If someone can produce debug information for this problem, it would be
> very helpful. I am not so good at debugging just by eyeballing code,
> though I will try to take a look next week some time.

Here's a partially redacted log of a delivery attempt. As far as I
can tell, no delivery attempt for the fw@??? recipient over
IPv4 is attempted.

2005-11-30 02:01:31 1EhMuA-0003QO-Se <= owner@??? U=qa P=local S=7043 id=E1EhMte-00076g-38@???
2005-11-30 02:01:32 1EhMuA-0003QO-Se mail.EXAMPLE.COM [192.0.2.25]: Connection refused
2005-11-30 02:01:32 1EhMuA-0003QO-Se == USER@??? R=dnslookup T=remote_smtp defer (111): Connection refused
2005-11-30 02:01:33 1EhMuA-0003QO-Se => USER@??? R=dnslookup T=remote_smtp H=gmail-smtp-in.l.google.com [64.233.185.27]
[...]
2005-11-30 02:01:37 1EhMuA-0003QO-Se mail.enyo.de [2001:14b0:202:1::a7]: No route to host
2005-11-30 02:01:37 1EhMuA-0003QO-Se == fw@??? R=dnslookup T=remote_smtp defer (113): No route to host
2005-11-30 02:01:37 1EhMuA-0003QO-Se ** fw@???: retry timeout exceeded
2005-11-30 02:01:37 1EhMuA-0003QO-Se ** USER@???: retry timeout exceeded
2005-11-30 02:01:37 1EhMuH-0003SO-ME <= <> R=1EhMuA-0003QO-Se U=Debian-exim P=local S=8007
2005-11-30 02:01:37 1EhMuA-0003QO-Se Completed

(mail.EXAMPLE.COM hasn't got an AAAA record.)

The problem is probably not related to multiple recipients; I've seen
instances where only a single recipient has been given.

Unfortunately, I haven't found a way to trigger the problem. I only
know it occurs from time to time. 8-(