This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mlalic
Recipients barry, mlalic, r.david.murray, serhiy.storchaka
Date 2013-06-20.21:25:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371763510.82.0.984349990824.issue18271@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-06-20 21:25:10mlalicsetrecipients: + mlalic, barry, r.david.murray, serhiy.storchaka
2013-06-20 21:25:10mlalicsetmessageid: <1371763510.82.0.984349990824.issue18271@psf.upfronthosting.co.za>
2013-06-20 21:25:10mlaliclinkissue18271 messages
2013-06-20 21:25:10mlaliccreate