Message299569
| Author |
r.david.murray |
| Recipients |
barry, r.david.murray, robertus |
| Date |
2017年07月31日.15:41:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1501515718.13.0.0952509703862.issue31089@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ah, I take it back. With \n it retains the \n in the decoded name field.
There is a bug of some sort here (\r\n should be treated the same as \n, I think, whatever way it is treated). I don't think this is worth addressing, given that the new policies provide a much better API for interacting with Messages, and you can in fact easily unfold the line before parsing it if you need to do it in 2.7:
>>> parseaddr(''.join(m['from'].splitlines()))
('=?UTF-8?Q?Anita_=W4=86ieckli=C5=84ska_|_PATO_Nieruch?= =?UTF-8?Q?omo=C5=9Bci?=', 'anita.wiecklinska@pato.com.pl') |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年07月31日 15:41:58 | r.david.murray | set | recipients:
+ r.david.murray, barry, robertus |
| 2017年07月31日 15:41:58 | r.david.murray | set | messageid: <1501515718.13.0.0952509703862.issue31089@psf.upfronthosting.co.za> |
| 2017年07月31日 15:41:58 | r.david.murray | link | issue31089 messages |
| 2017年07月31日 15:41:58 | r.david.murray | create |
|