iis smtp nntp: Hi All

I got a web application on IIS 6 with SMTP installed. The application sends
emails to
the web application subscribers. One of the users complains that he doesnt
get emails.
I searched the SMTP log and found the attached session :

OutboundConnectionResponse SMTPSVC1 MYWEB1 - 25 - - 250+Reset+OK 0 0 12 0
6187 SMTP - - - -
OutboundConnectionCommand SMTPSVC1 MYWEB1 - 25 MAIL -
FROM:<sender@mydomain.com> 0 0 4 0 6187 SMTP - - - -
OutboundConnectionResponse SMTPSVC1 MYWEB1 - 25 - - 250+OK 0 0 6 0 6265
SMTP - - - -
OutboundConnectionCommand SMTPSVC1 MYWEB1 - 25 RCPT -
TO:<someone@hisdomain.com> 0 0 4 0 6265 SMTP - - - -
OutboundConnectionResponse SMTPSVC1 MYWEB1 - 25 - - 250+Accepted 0 0 12 0
6359 SMTP - - - -
OutboundConnectionCommand SMTPSVC1 MYWEB1 - 25 DATA - - 0 0 4 0 6359
SMTP - - - -
OutboundConnectionResponse SMTPSVC1 MYWEB1 - 25 - -
354+Enter+message,+ending+with+"."+on+a+line+by+itself 0 0 54 0 6437
SMTP - - - -
OutboundConnectionResponse SMTPSVC1 MYWEB1 - 25 - -
250+OK+id=1HlhuR-00067e-3q 0 0 26 0 6562 SMTP - - - -
OutboundConnectionCommand SMTPSVC1 MYWEB1 - 25 RSET - - 0 0 4 0 6562
SMTP - - - -

From what I know about SMTP, the session should end with the QUIT command
and optionaly with the words "queued for delivery".

Does this session lines states that the message was sent or not?

Thanks.

[quoted text, click to view]

It was not delivered. The RSET command is not appropriate nor expected in
that context, and there is no proper 221 + QUIT present.

If you are using a valid sender (and you should be), you should get a
DSN. You can also run MS' smtpdiag to simulate a session with that remote
server.

Thank you, Sandy


[quoted text, click to view]