Autor: Todd Lyons Datum: To: James Mills CC: exim-users@exim.org Betreff: Re: [exim] strange resolver issue
On Sat, Oct 13, 2012 at 9:24 AM, James Mills <james.mills@???> wrote: > Hi Todd,
>
> I'm assuming the command you meant should've included -bh, since exim just sits waiting for
> input otherwise? Included the relevant output of that below:
Correct.
> host in hosts_connection_nolog? no (option unset)
> LOG: smtp_connection MAIN
> SMTP connection from [192.168.3.55]
> host in host_lookup? yes (matched "*")
> looking up host name for 192.168.3.55
> DNS lookup of 55.3.168.192.in-addr.arpa (PTR) succeeded
> IP address lookup yielded eeprobe.euroele.local
> no IP address found for host eeprobe.euroele.local (during SMTP connection from [192.168.3.55])
> LOG: host_lookup_failed MAIN
> no IP address found for host eeprobe.euroele.local (during SMTP connection from [192.168.3.55])
> no IP addresses found for eeprobe.euroele.local
> 192.168.3.55 does not match any IP address for eeprobe.euroele.local
I thought it would get a lot more output than that. Can you repeat it
with -d+all ?
> Interestingly, if I update the PTR and A records for eeprobe on the authoritative DNS server, such that they
> resolve to eeprobe.euroele.com (instead of local) then exim resolves these properly and doesn't
> complain at all. As soon as a switch it back to .local, it complains again. It seems to be there's
> something particular to the .local addresses that exim doesn't like resolving.
Yes that is an interesting data point.
...Todd
--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine