➜

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 maxking
Recipients barry, maxking, r.david.murray
Date 2017-11-27.00:03:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511740988.25.0.213398074469.issue32144@psf.upfronthosting.co.za>
In-reply-to
Content 
According to the documentation, email.policy.SMTP and .SMTPUTF8  should have CRLF (`\r\n`) as line endings for text/plain parts.

However, a new message parsed using message_from_binary_file with policy.SMTPUTF8 has `\n` as line endings for text/plain parts. This happens when I use get_content() on the new EmailMessage API.

Just to mention, in Python 2.7, the old `get_payload(decode=True)` returns the body with CRLF as line endings. However, in Python 3, `get_payload()` also returns '\n' as line endings.

Am I reading the documentation wrong?
History
Date User Action Args
2017-11-27 00:03:08maxkingsetrecipients: + maxking, barry, r.david.murray
2017-11-27 00:03:08maxkingsetmessageid: <1511740988.25.0.213398074469.issue32144@psf.upfronthosting.co.za>
2017-11-27 00:03:08maxkinglinkissue32144 messages
2017-11-27 00:03:08maxkingcreate