Re: [exim] (110): Connection timed out

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Heiko Schlittermann
Datum:  
To: exim-users
Betreff: Re: [exim] (110): Connection timed out
Hi,

Rob Gunther <redrob@???> (Do 13 Nov 2014 02:02:45 CET):

> 2014-11-12 15:59:22 1XoJ6d-0006S3-Io exchange.lahore.com [82.71.51.200]
> Connection timed out
> 2014-11-12 15:59:22 1XoJ6d-0006S3-Io == shahid@??? R=ik_router
> T=remote_smtp defer (110): Connection timed out
>
> A manual connection to the server via telnet works, I can connect and
> deliver mail.


Manual connecton from the server in question, I suppose.

> In rare situations where there is a routing issue or firewall issue I can
> clear the queue for a specific domain by routing mail pending for the


> # move mail to another server if it is stuck on this server for some reason
> clear_queue:
> driver = manualroute
> condition = ${if match{$domain}{lahore.com} }
> route_list = * "122.103.250.10"
> transport = remote_smtp
> no_more
>
> That normally will just direct any mail to another server and it is
> processed and delivered from there.
>
> This one specific domain, when I try the clear_queue router - it will
> report connection timed out. I know there is no firewall rules as I control
> both networks, no ISP block and these servers communicate all day long.


Just for my understanding, the clear_queue router and the associated
remote_smtp transport time out during the connection to the other data
center?

But the log lines above show the connection attempt from your server to
the mx in question.

So we got two issues: Why does the connection to the original MX time
out? AND why does the connection to the other data center time out?

BTW, the MX for lahore.com is not exchange.lahore.com but something
else. Maybe a special case handled by your ik_router

    Best regards from Dresden/Germany
    Viele Grüße aus Dresden
    Heiko Schlittermann
-- 
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
 gnupg fingerprint: 9288 F17D BBF9 9625 5ABC  285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2  7E92 EE4E AC98 48D0 359B)-