Am 29.10.2013 21:55, schrieb li...@rhsoft.net:
> Am 29.10.2013 21:46, schrieb Roman Gelfand:
>> How did you decide this is a network issue?
> 
> Connection timed out?

[harry@srv-rhsoft:~]$ telnet 96.57.168.248 25
Trying 96.57.168.248...
telnet: connect to address 96.57.168.248: Connection timed out

and BTW:

mail.domain.com[96.57.168.248]:25: Connection timed out

if you think you need to anonymize informations do *not*
use random domains: http://tools.ietf.org/html/rfc2606#section-3
and if you need help generally avoid to do so without
very good reasons

[harry@srv-rhsoft:~]$ host mail.domain.com
mail.domain.com has address 72.5.54.21

>> How would you go about determining which router which switch?
> 
> it's hard to explain how to debug network issues
> 
>> On Tue, Oct 29, 2013 at 4:33 PM, li...@rhsoft.net <li...@rhsoft.net> wrote:
>>>
>>>
>>> Am 29.10.2013 21:25, schrieb Roman Gelfand:
>>>> The client is thunderbird.  Correct me if I am wrong, it appears it 40
>>>> seconds for the client to hand over the email to the server?  If so,
>>>> where should I troubleshoot?  are there maintenance
>>>> tasks/configuration changes to improve this situation.
>>>>
>>>> BTW... from the inception there was no or negligible delay.  Several
>>>> months later, I am seeing this on regular basis even hourly volume is
>>>> not large.
>>>>
>>>> Oct 29 16:06:10 pmx1 postfix/smtp[7414]: 200AC43831:
>>>> to=<u...@domain.com>, relay=none, delay=40, delays=0.01/0/40/0,
>>>> dsn=4.4.1, status=deferred (connect to
>>>> mail.domain.com[96.57.168.248]:25: Connection timed out)
>>>
>>> this is clearly a *network* problem on the server *or* the client
>>> *or* somewhere between (routers, switches....)

Reply via email to