On Thu, 23 Jun 2005 20:57:07 -0500, John Traweek
<[log in to unmask]> wrote:

>17:48:11 mail.SRIGLOBALIMPORTS.COM( 13) <<< .
>17:48:42 ( 13)O closed SRIGLOBALIMPORTS.COM mail.SRIGLOBALIMPORTS.COM,
>WSAETIMEDOUT

Note that a WSAETIMEDOUT error means the TCP connection was lost or
terminated by the other side.

>You can see that LSMTP simply waits for 30 secs and never hears back.  I
>would normally attribute this to an over worked mail server, but I am
>literally getting at least one or two complaints every other day now.  Has
>anyone seen this before, or has started to see more and more of this?

This is a question specific to LSMTP and thus more appropriate to the
LSMTP-L list.  But what is happening is really exactly the same as the
situation with the PIX.

From your own posting long ago about PIX problem, the condition the same.

06:39:31 dns1.AIMNETSOLUTIONS.COM( 18) >>> 354 Enter mail, end with "." on a
line by itself
06:39:31 dns1.AIMNETSOLUTIONS.COM( 18) <<< .
06:49:31 ( 18)O opened AIMNETSOLUTIONS.COM dns2.AIMNETSOLUTIONS.COM

As you can see the lack of a 250 OK response by the receiving mail server
requires LSMTP (or any other sensible mail server) to think the transaction
failed and to retry it, resulting in duplicate deliveries.

This is either a configuration mistake on their part (the mailer is MDaemon
8.0.2) or a seriously misguided attempt at some "clever" anti-spam trick.

The way to stop complaints is to stop mailing to this domain. 

Try a manual resolve in the LSMTP resolver on this domain or a telnet port
25 from the command line.  Their server exhibits the same behavior (lack of
response).