This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davidstrauss
Recipients davidstrauss
Date 2011-04-27.03:49:16
SpamBayes Score 0.0036224758
Marked as misclassified No
Message-id <1303876157.91.0.419040488355.issue11932@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2011-04-27 03:49:17davidstrausssetrecipients: + davidstrauss
2011-04-27 03:49:17davidstrausssetmessageid: <1303876157.91.0.419040488355.issue11932@psf.upfronthosting.co.za>
2011-04-27 03:49:16davidstrausslinkissue11932 messages
2011-04-27 03:49:16davidstrausscreate