Author: Kevin P. Fleming Date: To: exim-users Subject: Re: [Exim] Exim 4.10 sender verify callout using low-priority MX
record
Hmmm... the problem appears to be some type of timeout connecting back
to the sending server. I'm investigating now... I know it's not ident,
but it could be reverse DNS.
Philip Hazel wrote: > On Fri, 2 Aug 2002, Kevin P. Fleming wrote:
>
>
>>I've got an Exim 4.10 server with sender callout verification enabled in
>>an ACL. Another server that I also maintain, for a different domain, is
>>trying to send mail to the first server. The first server is reporting a
>>temporary error: "Sender callout verification timed out". There is only
>>one mail server for the sending domain, and I can't see _any_ attempt
>>for sender verification arriving at the sending server.
>
>
> The only way to track this down is going to be to run some debugging on
> the 4.10 server.
>
>
>>For some reason, Exim on the receiving server is trying to do the sender
>>verification callout to the priority 10 server, not the priority 5
>>server. The priority 10 server doesn't exist any more, so having it
>>still in DNS is my problem... but I don't understand why Exim is not
>>using the primary server MX record for the callout. It most certainly
>>can connect to that server, as the original message is being delivered
>>from that server.
>
>
> Strictly, "can receive a connection from" is not the same as "can
> connect to". Are there any firewalls or suchlike in the way?
>
>
>
