RE: [Exim] Re: Selective retry timeout exceeded

Page principale
Supprimer ce message
Répondre à ce message
Auteur: PEAR Bruntjen
Date:  
À: Exim-Users@Exim. Org
CC: Pbarnwell@Lionbytes. Co. Uk
Sujet: RE: [Exim] Re: Selective retry timeout exceeded
Thanks for the assistance. It turned out not to be an Exim problem but
rather a firewall configuration issue. A new firewall was not allowing
incoming finger requests so the other servers could not authenticate and
refused the email.

Thanks again for the help.

Eric

Eric Bruntjen
Computer Specialist
USDA-ARS Yakima Agricultural Research Laboratory
mailto:ebruntjen@yarl.ars.usda.gov
http://www.yarl.prosser.wsu.edu/Support_Services/Computers/Comp_Main.htm
Phone: (509) 454-6562
Fax: (509) 454-5646

-----Original Message-----
From: Pete Barnwell [mailto:pbarnwell@lionbytes.co.uk]
Sent: Thursday, January 03, 2002 10:48
To: PEAR Bruntjen
Subject: Re: [Exim] Re: Selective retry timeout exceeded

PEAR Bruntjen wrote:

>>So you cannot connect to 199.133.48.254. This does not seem to be an
>>Exim problem, but some kind of networking problem. From here, I can
>>connect, though the server is clearly paranoid:
>>
>
>>$ telnet 199.133.48.254 25
>>Trying 199.133.48.254...
>>Connected to 199.133.48.254.
>>Escape character is '^]'.
>>220
>>
>

****************************************************************************
> ***
>
>
>>Have you tried the network testing tools such as ping and traceroute?
>>Have you tried "telnet 199.133.48.254 25"
>>
>
> Yes, we've tried telnet, ping, traceroute, etc. He can always connect. I
> don't believe this is an Exim problem anymore either but the admin at
> 199.133.48.254 insists that it is.
> Thanks for your help.
>
> Eric



Given that you don't think this is still an Exim problem, I'll put in my
$0.02...

A similar problem surfaced on the Postfix list about a month back, with
people having trouble sending to hosts behind a PIX firewall -a lot of
traffic was generated trying to solve it. I would suggest that a look
through the Postfix archives might provide the information you require.

That's the good? news -the bad is that although it really is a PIX
problem the only workaround that surfaced was a patch to Postfix - AFAIR
the trick is to introduce a delay into the connection (I haven't found
it a problem so I didn't read it too carefully...).


http://groups.google.com/groups?q=PIX&hl=en&group=mailing.postfix.users&rnum
=4&selm=9f1cm1%241th0%241%40FreeBSD.csie.NCTU.edu.tw

Actually, having had a quick glance through, I'm not now so sure this is
the problem you've got, but you never know...

Hope this is of some use.

Pete