David Strauss added the comment:
Never mind. I was manipulating some text that broke the parser.
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
David Strauss added the comment:
Replacing the file with a proper example.
--
Added file: http://bugs.python.org/file21790/wrapped_multipart.txt
___
Python tracker
<http://bugs.python.org/issue11
Changes by David Strauss :
Removed file: http://bugs.python.org/file21789/wrapped_multipart.txt
___
Python tracker
<http://bugs.python.org/issue11932>
___
___
Python-bug
New submission from David Strauss :
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
