Message79938
Your example header is invalid. Excerpt from RFC2047 <http://
www.ietf.org/rfc/rfc2047.txt> 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 <http://www.activestate.com/ASPN/Python/Cookbook/>
I'd close this report as invalid. |
|
Date |
User |
Action |
Args |
2009-03-09 14:29:49 | georg.brandl | set | spambayes_score: 0.701537 -> 0.0 |
2009-01-16 07:32:09 | ggenellina | set | recipients:
+ ggenellina, oxij |
2009-01-16 07:32:08 | ggenellina | set | messageid: <1232091128.83.0.960785105517.issue4958@psf.upfronthosting.co.za> |
2009-01-16 07:32:07 | ggenellina | link | issue4958 messages |
2009-01-16 07:32:04 | ggenellina | create | |
|