From: Wietse Venema (no email)
Date: Thu Dec 01 2005 - 12:34:56 EST
dogbert:
[ Charset ISO-8859-1 unsupported, converting... ]
> Wietse Venema wrote:
> > Wietse:
> >>> To diagnose the problem you will need to record a failed session
> >>> with, for example tcpdump. Record the full packet content:
> >>>
> >>> tcpdump -s 2000 -i interface -w /file/name
> >>>
> >>> There has been a recent flurry of "timeout after DATA" problems
> >>> with MS Exchange 5 because it was sending mail that did not end in
> >>> "<CR><LF>.<CR><LF>".
> >
> > dogbert:
> >> I've analyzed some sessions with Ethereal and found that the main difference
> >> between a working mail (that pass through postifx) and a bad message (that
> >> stuck) is that the latter doesn't terminate with a \r\n.\r\n but with a packet
> >> of EOM (if I decode with ethereal the full SMTP transmission it contain the last
> >> . for ending the session but it is not present in the MESSAGE BODY part of the
> >> session).
> >
> > What is EOM?
> >
> > Can I see the data that is actually sent? I hate it when helpful
> > software changes the evidence.
> >
> > If the mail does not end in "<CR><LF>.<CR><LF>" then it does
> > not comply with the SMTP protocol, and all bets are off.
> >
> > Wietse
> >
>
> I believe that EOM stand for End Of Message and I hope that if Ethereal can
> understand is as part of an SMTP transaction it somehow comply with smtp standard.
If the text does not end on "<CR><LF>.<CR><LF>" then it does not
comply with SMTP.
Can I have a copy of the UNENCODED recording of a session that
fails with "timeout after DATA".
Can I have a copy of the logging that corresponds to that failed
delivery.
Wietse
|
|
|