Message117434
| Author |
tkikuchi |
| Recipients |
barry, ggenellina, ishimoto, jafo, kael, leromarinvit, r.david.murray, tkikuchi, tlynn, tony_nelson |
| Date |
2010年09月27日.01:18:17 |
| SpamBayes Score |
0.0054822904 |
| Marked as misclassified |
No |
| Message-id |
<1285550301.24.0.72201925086.issue1079@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Hi, all
I am against applying these patches because they will insert space separations in re-composed header (with str() function).
Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord
-> [('Sm', None), ('\xf6', 'iso-8859-1'), ('rg', None), ('\xe5', 'iso-8859-1'), ('sbord', None)]
-> Sm =?iso-8859-1?q?=F6?= rg =?iso-8859-1?q?=E5?= sbord
Instead, I submit a small recipe for decoding non-compliant RFC2047 header where space separation is not properly inserted between encoded_word and us-ascii characters.
Please try! |
|