Re: [exim] Strange failure mailing exim-dev list

Top Page
Delete this message
Reply to this message
Author: Tony Finch
Date:  
To: Marc Sherman
CC: exim-users
Subject: Re: [exim] Strange failure mailing exim-dev list
On Tue, 14 Jun 2005, Marc Sherman wrote:
>
> Here's the sesame.csx.cam.ac.uk entry from my retry database:
> T:sesame.csx.cam.ac.uk:2001:630:200:8080:20e:cff:fe09:a58a 113 77 No route to host
> 01-Jun-2005 09:14:50 13-Jun-2005 14:55:56 13-Jun-2005 20:55:56 *


I had a sneaking suspicion it would be an IPv6 problem :-(

> The very first entry in my exim.conf main section is:
>     dns_ipv4_lookup = *
> so I remain confused.  Why is it trying to connect to an ipv6 address for
> sesame when I've configured it to only lookup ipv4?


    dns_ipv4_config is a fudge to help with name servers that give big delays or
    otherwise do not work for the new IPv6 record types. If Exim is handed an
    IPv6 address record as a result of an MX lookup, it always recognizes it,
    and may as a result make an outgoing IPv6 connection. All this option does
    is to make Exim look only for IPv4-style A records when it needs to find
    an IP address for a host name. In due course, when the world's name
    servers have all been upgraded, there should be no need for this option.


The question is why Exim is not falling back to the IPv4 address properly.

I suppose a workaround would be to add ::/0 to your ignore_target_hosts.

Tony.
--
<fanf@???> <dot@???> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}