[Mono-bugs] [Bug 81869][Nor] Changed - System.Net.Mail.SmtpClient is not doing any rfc 2047 encoding on headers

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by fejj at novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=81869

--- shadow/81869	2007-07-06 12:27:35.000000000 -0400
+++ shadow/81869.tmp.19354	2007-07-06 13:07:05.000000000 -0400
@@ -33,6 +33,28 @@
 
 The generated subject line will only be readable if the recipient's MUA
 guesses the encoding.
 
 ------- Additional Comments From miguel at ximian.com  2007-07-06 12:27 -------
 Jeff, could you provide us with some feedback?
+
+------- Additional Comments From fejj at novell.com  2007-07-06 13:07 -------
+ok, looking at MailMessage and SmtpClient I want to smack Microsoft
+for this design... but, here's what needs to be done afaict:
+
+MailMessage's public API doesn't allow for getting the encoded
+versions of Subject nor any of the From/To/Cc addresses, so I suppose
+that either SmtpClient will have to implement RFC2047 encoding rules
+or perhaps MailMessage can have an internal method/property to return
+the encoded subject string.
+
+MailAddress[Collection] will each need to have to have an internal
+method/property to return the rfc2047 encoded strings because the
+DisplayNameEncoding used by MailAddress is not publicly accessable
+afaict from the msdn docs.
+
+perhaps I can implement this sometime soon, if not... anyone
+interested in fixing this should see:
+
+http://www.ietf.org/rfc/rfc2047.txt
+
+for the proper encoding rules.