On Sun, 2005-02-27 at 00:06 +0100, Marc Haber wrote: >this is Debian Bug #296492, which I consider a bug with normal >severity from a Debian point of view. > >----- Forwarded message from Laurent Fousse <[EMAIL PROTECTED]> ----- > >> When sending to a remote host that has both an ipv6 and ipv4 RR, exim >> falls back immediately to ipv4 when ipv6 connectivity is not present. >> I noticed however that exim is stuck to ipv6 when it's trying to send >> to a "fallback_host".
Pleae define 'stuck to' in this context. Surely Exim should attempt to use all addresses in the RR set for the named fallback_host? Does it try only the first and then give up? If the first address returned from getaddrinfo() is the IPv6 address and you don't have a global IPv6 address of your own, then your resolver isn't conforming to RFC3484. Nevertheless, the failure to connect to the IPv6 address(es) should be fairly much instant, and we should fall back to the other address(es). Please could you describe the problem in more detail? -- dwmw2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
