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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81869 --- shadow/81869 2007-06-13 11:47:32.000000000 -0400 +++ shadow/81869.tmp.30762 2007-06-13 11:47:32.000000000 -0400 @@ -0,0 +1,35 @@ +Bug#: 81869 +Product: Mono: Class Libraries +Version: 1.2 +OS: GNU/Linux [Other] +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Normal +Component: System +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: System.Net.Mail.SmtpClient is not doing any rfc 2047 encoding on headers + +Headers generated by System.Net.Mail.SmtpClient aren't being rfc2047 +encoded at all, so setting any of them (Subject, DisplayName on any +address, ...) with non ascii characters will generate a message that +violates rfc 2822. + +The deprecated System.Web.Mail.SmtpClient did at least do some simple +encoding (though it always defaults to base64). + +Simple test case: + +System.Net.Mail.SmtpClient client = new +System.Net.Mail.SmtpClient("localhost", 25); +client.Send("[EMAIL PROTECTED]", "[EMAIL PROTECTED]", "Subjet with non +ascii content áéíóú.", "body"); + +The generated subject line will only be readable if the recipient's MUA +guesses the encoding.
_______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
