To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77449
------- Additional comments from [EMAIL PROTECTED] Wed Jun 13 09:31:47 +0000 2007 ------- A few quick comments on the attached mailmerge.nonascii-0.2.patch: - No longer sure whether Optional<string> SenderName vs. just string SenderName is a good idea, see <http://groups.google.com/group/comp.mail.headers/browse_thread/thread/ca7f9b88b4a89769/0b72222d7c365294#0b72222d7c365294>. Sorry if that caused any extra work. - The documentation of XMailMessage SenderAddress should be fixed to state that it must be a valid RFC 2822 mailbox. Who guarantees that it really is one? Can there be security problems if it is not/should the Python code check? - hdr = Header(sendername.Value,'utf-8') probably does not take into account that the resulting hdr must be a valid RFC 2822 phrase (i.e., will probably not escape problematic ASCII characters like '<' or '(' or '"' in sendername.Value). - The resulting XMailMessage looks odd: SenderName/SenderAddress can now unambiguously transport the information necessary to create a RFC 2822 From: header, but what about the other addresses involved (ReplyToAddress, addRecipient, addCcRecipient, addBccRecipient)? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
