Skip to content

Commit cb5c802

Browse files
dlaxserverwentdown
andauthored
Fix id of 'Internet Message Format' RFC in email doc (pythonGH-24137)
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 29d1bc0 in which the ID of this RFC got updated from the obsolete 2822.) Co-authored-by: Ambrose Chua <[email protected]>
1 parent 0d930f1 commit cb5c802

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

Doc/library/email.compat32-message.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ policy :attr:`~email.policy.Compat32`. If you are going to use another policy,
2323
you should be using the :class:`~email.message.EmailMessage` class instead.
2424

2525
An email message consists of *headers* and a *payload*. Headers must be
26-
:rfc:`5233` style names and values, where the field name and value are
26+
:rfc:`5322` style names and values, where the field name and value are
2727
separated by a colon. The colon is not part of either the field name or the
2828
field value. The payload may be a simple text message, or a binary object, or
2929
a structured sequence of sub-messages each with their own set of headers and

Doc/library/email.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The :mod:`email` package is a library for managing email messages. It is
1616
specifically *not* designed to do any sending of email messages to SMTP
1717
(:rfc:`2821`), NNTP, or other servers; those are functions of modules such as
1818
:mod:`smtplib` and :mod:`nntplib`. The :mod:`email` package attempts to be as
19-
RFC-compliant as possible, supporting :rfc:`5233` and :rfc:`6532`, as well as
19+
RFC-compliant as possible, supporting :rfc:`5322` and :rfc:`6532`, as well as
2020
such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :rfc:`2183`,
2121
and :rfc:`2231`.
2222

0 commit comments

Comments
 (0)