[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

Thanks for the patches.  I didn't use them, but they were helpful references.

This is in a grey area between a bug and a feature request.  The fact is, though, that for the most part the email module currently doesn't make extra effort to detect defects, it just reports the ones it has to work around.  The only exception I found to this was taking an extra step to report a defect that represented a defect in the constructed model of the message.

Now, in the next version of email (targeted for 3.3), one of the design goals is to detect as many RFC conformance defects as practical.  So, I'm treating this as a feature request, and have checked it in to 3.3 (default).

----------
resolution:  -> accepted
stage:  -> committed/rejected
status: open -> closed
type: behavior -> feature request
versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1874>
_______________________________________