New submission from David Strauss <da...@davidstrauss.net>: I've attached a multipart message produced by Thunderbird. For some reason, the email.message parser doesn't properly recognize the boundary. This causes legitimate multipart messages to parse as if no boundary were specified. Simply removing the newline on the line starting with " boundary" allows it to parse correctly.
To see why this is valid, refer to section 2.2.3 of RFC2822 [1]. [1] http://tools.ietf.org/html/rfc2822#section-2.2.3 ---------- components: Library (Lib) files: wrapped_multipart.txt messages: 134523 nosy: davidstrauss priority: normal severity: normal status: open title: Email multipart boundary detection fails on a wrapped header type: behavior versions: Python 2.6, Python 2.7 Added file: http://bugs.python.org/file21789/wrapped_multipart.txt _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11932> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
