Message207033
Nevermind, I failed to notice the message_from_string part of the traceback.
Different question: what are you doing with the message after you parse it? It is not an RFC valid message if you parse it from a string, so the only way to make it produce an RFC valid output is if you emit it as a string *and* encode the output to utf-8.
I'll have to think about how this "should" work...a clearer error message may be the answer, but if so I suppose I'll need an actual deprecation period before shipping the charset fix for set_payload. |
|
Date |
User |
Action |
Args |
2013-12-28 15:47:35 | r.david.murray | set | recipients:
+ r.david.murray, barry, apollo13 |
2013-12-28 15:47:35 | r.david.murray | set | messageid: <1388245655.25.0.74305156287.issue20089@psf.upfronthosting.co.za> |
2013-12-28 15:47:35 | r.david.murray | link | issue20089 messages |
2013-12-28 15:47:34 | r.david.murray | create | |
|