From: Tony Earnshaw (no email)
Date: Wed Dec 01 2004 - 07:46:08 EST
tir, 30.11.2004 kl. 23.54 skrev John Madden:
> > Absolutely not, with any Exim server anywhere; neither with this 2.1.5
> > semi-production rig or production 2.1.5 rigs.
>
> But what about varying versions of Exim? I'm finding that only very recent
> versions even have this protocol verification option, and perhaps a bug lies
> within. I probably send to thousands of Exim servers everyday and only see
> this with those running things like debian/testing.
All versions. I used to be an Exim mailadmin and still keep a sharp eye
on what's going on in that camp. With regard to rfc1413 ident, each Exim
mailadmin can choose whether to implement it or not - it's off by
default. Exim 4.30's spec.txt says:
Although they are cheap and can provide
useful information for tracing problem
messages, some hosts and firewalls have
problems with ident calls. This can
result in a timeout instead of an immediate
refused connection, leading to
delays on starting up an incoming SMTP
session.
> > 220 shampoo.ca ESMTP Exim 4.34 Tue, 30 Nov 2004 09:19:18 -0500
> > quit
> > 221 shampoo.ca closing connection
> > Connection closed by foreign host.
> >
> > Immediate connection.
>
> The TCP connection is immediate, but the SMTP banner coming back isn't --
> takes perhaps 30 or 40 seconds on my end. I assume this is where the "read
> timeout" is coming from, but my smtp_connect_timeout is now 90 seconds, so I
> can't be sure on that one.
Here the smtp banner came up immediately - iptables gives a REJECT for
traffic to/from port 113..
If what you are experiencing were universal with postfix 2.1.x, more
people would be posting about it.
--Tonni
-- Nothing sucksseeds like a pigeon without a beak ... mail: http://www.billy.demon.nl They love us, don't they, They feed us, won't they ...
|
|
|