Message191540
Thank you for your reply.
Unfortunately, I have a use case where message_from_bytes has a pretty great disadvantage. I have to parse the received message and then forward it completely unchanged, apart from possibly adding a few new headers. The problem with message_from_bytes is that it changes the Content-Transfer-Encoding header to base64 (and consequently base64 encodes the content).
Do you possibly have a suggestion how to currently go about solving this problem? A possible solution I can spot from your answer is to check the Content-Transfer-Encoding before getting the payload and use the version without decode=True when it is 8bit. Maybe there is something more elegant?
Thank you in advance. |
|
Date |
User |
Action |
Args |
2013-06-20 21:25:10 | mlalic | set | recipients:
+ mlalic, barry, r.david.murray, serhiy.storchaka |
2013-06-20 21:25:10 | mlalic | set | messageid: <1371763510.82.0.984349990824.issue18271@psf.upfronthosting.co.za> |
2013-06-20 21:25:10 | mlalic | link | issue18271 messages |
2013-06-20 21:25:10 | mlalic | create | |
|