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 r.david.murray
Recipients Claudiu Saftoiu, CryptidVulpes, r.david.murray
Date 2016-07-29.14:09:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Returning the undecoded payload is a good idea.  Let's go with that.

The email module, unlike most stdlib packages, has a mandate that the parser should never raise an error.  Instead we do our best to guess (very unlike everything else in python!) and note 'defects' in the message.  The reason this is the case is Postel's Law, which has become one of the guiding principles in dealing with email over the years: "be conservative in what you do, and generous in what you accept".  So, the generator will raise errors (if the original input didn't come from the parser), but the parser will not, if at all possible.

(For those who want aggressive error checking, python3 the 'raise_on_defect' policy setting.)

For the versions, we use that field to indicate which versions the bug will get fixed in, which is why I removed 3.4.
Date User Action Args
2016-07-29 14:09:16r.david.murraysetrecipients: + r.david.murray, Claudiu Saftoiu, CryptidVulpes
2016-07-29 14:09:15r.david.murraysetmessageid: <>
2016-07-29 14:09:15r.david.murraylinkissue27397 messages
2016-07-29 14:09:15r.david.murraycreate