| malcolmct 2006-09-22, 7:27 pm |
| We're using Exchange 2003 SP2 and have a client company which has an Exchange
server (not sure of which version) that is unable to send us mail. Incoming
mail from everywhere else flows in without a problem.
Here's the SMTP conversation of a typical failed session:
220 exchange2.abc.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at Fri, 22 Sep 2006 12:00:28 -0400
EHLO exchange.xyz.local
250-exchange2.abc.com Hello [123.45.67.89]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
MAIL FROM:<jsmith@xyz.com>
250 2.1.0 jsmith@xyz.com....Sender OK
RCPT TO:<ajones@abc.com>
250 2.1.5 ajones@abc.com
XEXCH50 2020 2
504 Need to authenticate first
BDAT 3968 LAST
After this the session simply times out.
As I understand it, the sending server should simply continue sending data
at that point. Instead it just gives up.
Here's a similar SMTP conversation with another client's server which has no
problem at all:
220 exchange2.abc.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at Fri, 22 Sep 2006 13:04:21 -0400
EHLO EXCHANGE.hij.com
250-exchange2.abc.com Hello [98.76.54.32]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
MAIL FROM:<fbrown@hij.com>
250 2.1.0 fbrown@hij.com....Sender OK
RCPT TO:<bgreen@abc.com> NOTIFY=NEVER
250 2.1.5 bgreen@abc.com
XEXCH50 2860 2
504 Need to authenticate first
BDAT 1446 LAST
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:mdn
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=disposition-notification;
boundary="----_=_NextPart_001_01C6DE69.25E3DEB7"
Subject: Read: RE: Hello again
Date: Fri, 22 Sep 2006 13:04:21 -0400
....etc., etc.
It seems to me that the problem is probably at our client's end, but can
anybody please suggest what might be wrong, so that I can pass it along to
the client's Exchange administrator.
Many thanks,
Malcolm
|