https://github.com/python/cpython/commit/28d3f7a3aff31c826e605d687256a95c7db... commit: 28d3f7a3aff31c826e605d687256a95c7db373b1 branch: 3.8 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: orsenthil <skumaran@gatech.edu> date: 2021-04-25T18:42:27-07:00 summary: Fix id of 'Internet Message Format' RFC in email doc GH-25614 Previous ID (5233) refers to "Sieve Email Filtering: Subaddress Extension". It seems that the actual reference should be "Internet Message Format" RFC 5322 (https://tools.ietf.org/html/rfc5322). (The typo probably comes from commit 29d1bc0842 in which the ID of this RFC got updated from the obsolete 2822.) Co-authored-by: Ambrose Chua <ambrose@hey.com> (cherry picked from commit cb5c802dcf8851663c4eac5d73f968f626a3a1dc) Co-authored-by: Denis Laxalde <denis@laxalde.org> files: M Doc/library/email.compat32-message.rst M Doc/library/email.rst diff --git a/Doc/library/email.compat32-message.rst b/Doc/library/email.compat32-message.rst index 745b3a6a3ad42..c68e773b1688a 100644 --- a/Doc/library/email.compat32-message.rst +++ b/Doc/library/email.compat32-message.rst @@ -23,7 +23,7 @@ policy :attr:`~email.policy.Compat32`. If you are going to use another policy, you should be using the :class:`~email.message.EmailMessage` class instead. An email message consists of *headers* and a *payload*. Headers must be -:rfc:`5233` style names and values, where the field name and value are +:rfc:`5322` style names and values, where the field name and value are separated by a colon. The colon is not part of either the field name or the field value. The payload may be a simple text message, or a binary object, or a structured sequence of sub-messages each with their own set of headers and diff --git a/Doc/library/email.rst b/Doc/library/email.rst index fae99cf3e6abb..5eebcd9e896d9 100644 --- a/Doc/library/email.rst +++ b/Doc/library/email.rst @@ -16,7 +16,7 @@ The :mod:`email` package is a library for managing email messages. It is specifically *not* designed to do any sending of email messages to SMTP (:rfc:`2821`), NNTP, or other servers; those are functions of modules such as :mod:`smtplib` and :mod:`nntplib`. The :mod:`email` package attempts to be as -RFC-compliant as possible, supporting :rfc:`5233` and :rfc:`6532`, as well as +RFC-compliant as possible, supporting :rfc:`5322` and :rfc:`6532`, as well as such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :rfc:`2183`, and :rfc:`2231`.