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 ivyl
Recipients barry, ivyl, r.david.murray
Date 2020-05-11.19:00:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589223619.93.0.38032538849.issue40597@roundup.psfhosted.org>
In-reply-to
Content
RFC5322[0] in section 2.1.1 mandates that the line cannot be longer than 998 characters and should not be longer than 78 characters (excluding CRLF). When we use raw_data_manager (default for EmailPolicy, EmailMessage) it does the correct thing as long as the message contains characters outside of 7bit US-ASCII set - base64 or qp Content-Transfer-Encoding which respects the line wrapping at 78 characters.

However if our message is limited the characters from the 7bit US-ASCII set no transfer encoding is applied, and such messages can easily go beyond 78 or even 998 characters.


[0]: https://tools.ietf.org/html/rfc5322.html#section-2.1.1
History
Date User Action Args
2020-05-11 19:00:20ivylsetrecipients: + ivyl, barry, r.david.murray
2020-05-11 19:00:19ivylsetmessageid: <1589223619.93.0.38032538849.issue40597@roundup.psfhosted.org>
2020-05-11 19:00:19ivyllinkissue40597 messages
2020-05-11 19:00:19ivylcreate