Parsing an email containing a multipart Content-Type, along with a Content-Transfer-Encoding containing an invalid (non-ASCII-decodable) byte will fail.email.feedparser.FeedParser._parsegen() calls "self._cur.get('content-transfer-encoding', '8bit')" to get the header.It then tries to check whether the C-T-E is in the allowable set of ('7bit', '8bit', 'binary'), and to do so case-insensitively, it tries to convert the header to lowercase. However, because there's an invalid character in there, it's dealing with a Header object rather than a str. Hence it throws an AttributeError.Correct behaviour would be to convert the Header to a str, see that it's not valid, and continue on to handle the defect as usual.Thanks to Daniel Axtens for finding this bug as he was running the AFL fuzzer on the email parsing code in Patchwork (https://github.com/getpatchwork/patchwork).Pull request incoming.

There's a deeper problem here involving how Header is used in compat32 that I've been aware of for a while but haven't had time to try to think through a fix for (there may not be one, given the history of the compat32 code).  In the meantime, the proposed fix is reasonable.  (It isn't needed for the new policies, but it doesn't hurt.)

New changesetaa79707262f893428665ef45b5e879129abca4aa by Barry Warsaw (Abhilash Raj) in branch 'master':bpo-30835: email: Fix AttributeError when parsing invalid CTE (GH-13598)https://github.com/python/cpython/commit/aa79707262f893428665ef45b5e879129abca4aa

New changesetf62a372928fbf6a2ba722f12f069b75ca6ad16fb by Miss Islington (bot) in branch '3.7':bpo-30835: email: Fix AttributeError when parsing invalid CTE (GH-13598)https://github.com/python/cpython/commit/f62a372928fbf6a2ba722f12f069b75ca6ad16fb