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 ggenellina
Recipients ggenellina, oxij
Date 2009-01-16.07:32:03
SpamBayes Score 0.0
Marked as misclassified No
Message-id <>
Your example header is invalid. Excerpt from RFC2047 <http://> section 5:

   + An 'encoded-word' MUST NOT be used in parameter of a MIME
     Content-Type or Content-Disposition field, or in any structured
     field body except within a 'comment' or 'phrase'.

Even in the places where an "encoded word" (the sequence =?...?=) is 
allowed, it must always be surrounded by whitespace -- this is by 
design in the RFC.

If you have many of those invalid headers, you'll have to "cook" the 
output of decode_header, posibly detecting malformed sequences and 
calling decode_header again with just the offending substring. 

I don't think that Python should accept malformed headers - but if you 
come to a good solution you may publish the recipe in the Python 
cookbook <>

I'd close this report as invalid.
Date User Action Args
2009-03-09 14:29:49georg.brandlsetspambayes_score: 0.701537 -> 0.0
2009-01-16 07:32:09ggenellinasetrecipients: + ggenellina, oxij
2009-01-16 07:32:08ggenellinasetmessageid: <>
2009-01-16 07:32:07ggenellinalinkissue4958 messages
2009-01-16 07:32:04ggenellinacreate