System.Net.Mail is not RFC2821 compliant

[Guest]

Hi!

I'm playing around with System.Net.Mail in .Net 2.0 and noticed that it
never sends the QUIT command.

Using a network sniffer I checked and immidiatly after it has received the
confirmation of the mail being accepted, it disconnects.

RFC2821 4.1.1.10 says:
"The sender MUST NOT intentionally close the transmission channel until it
sends a QUIT command and SHOULD wait until it receives the reply (even if
there was an error response to a previous command)."

Is there anyway to make System.Net.Mail RFC 2821 compliant?

Regards,

John

 

[Walter Wang [MSFT]]

Hi John,

I've done some searching in our internal database and we already have an
open bug report for this issue. We're sorry for the inconvenience caused
and thank you for your feedback.

Due to some design change, the issue currently is still under discussion
when to fix it. If this issue is critical for your project, please contact
our Customer Support and Service for further support. Thanks for your
understanding.

Please feel free to let me know if there's anything I can help.


Regards,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.