On Mon, Mar 18, 2002, Lance Nehring wrote:
> Yes, I see the same thing in my headers.
> I've also addressed this to <[EMAIL PROTECTED]> to try to get
> their attention to investigate their email logs.
> A valid STMP host on the net should route the postmaster address to an admin.
> per RFC822.
>
> Sometimes mmx.engelschall.com shows up in the header as:
>
> Received: from mmx.engelschall.com [195.27.130.252] by
> cmsmail05.cms.usa.net via smtad
> (CM.1201.1.04.PATCH); Mon, 18 Mar 2002 15:02:36 GMT
>
> other times it shows up as:
>
> Received: from mmx.engelschall.com [195.27.130.252] by
> cmsmail06.cms.usa.net via smtad
> (CM.1201.1.04); Mon, 18 Mar 2002 14:05:36 GMT
>
> It does look like a good place to look for the problem but will require
> assistence from engelschall.com.
> [...]
mmx.engelschall.com is the Postfix+SMTPfeed service for the mass-mail
delivery of our mailing list subscriptions which is also used by
OpenSSL. According to the Postfix logfile for this particular mail and
the receiving MTA, it is the problem of the receiving MTA or the network
connection to it:
| Mar 18 10:27:36 <info> postfix/lmtp[83321]: 57F961950B: to=<[EMAIL PROTECTED]>,
| relay=127.0.0.1[127.0.0.1], delay=863, status=deferred (conversation with
| 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be
| sent more than once)
| Mar 18 11:14:22 <info> postfix/lmtp[85311]: 57F961950B: to=<[EMAIL PROTECTED]>,
| relay=127.0.0.1[127.0.0.1], delay=3668, status=deferred (conversation with
| 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be
| sent more than once)
| Mar 18 12:43:59 <info> postfix/lmtp[87921]: 57F961950B: to=<[EMAIL PROTECTED]>,
| relay=127.0.0.1[127.0.0.1], delay=9046, status=deferred (conversation with
| 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be
| sent more than once)
| Mar 18 15:13:55 <info> postfix/lmtp[92784]: 57F961950B: to=<[EMAIL PROTECTED]>,
| relay=127.0.0.1[127.0.0.1], delay=18042, status=deferred (conversation with
| 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be
| sent more than once)
| Mar 18 17:44:06 <info> postfix/lmtp[99370]: 57F961950B: to=<[EMAIL PROTECTED]>,
| relay=127.0.0.1[127.0.0.1], delay=27053, status=deferred (conversation with
| 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be
| sent more than once)
As you can see, SMTPfeed (the LMTP service reported here by Postfix) on
mmx.engelschall.com tried many times to deliver the message because the
connection timed out in the middle of the SMTP conversation. And, yes,
as the log also says, the result could be that the message is received
by the peer more than once. So, that's the expected behaviour in this
case and nothing is wrong -- at least not on the mmx.engelschall.com
side as far as I can see it.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
