Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 3501, "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", March 2003

Note: This RFC has been obsoleted by RFC 9051

Note: This RFC has been updated by RFC 4466, RFC 4469, RFC 4551, RFC 5032, RFC 5182, RFC 5738, RFC 6186, RFC 6858, RFC 7817, RFC 8314, RFC 8437, RFC 8474, RFC 8996

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

---

Errata ID: 6636
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: TornaxO7
Date Reported: 2021-07-10
Rejected by: Benjamin Kaduk
Date Rejected: 2021-07-21

Throughout the document, when it says:

   IMAP4rev1 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching,
   and selective fetching of message attributes, texts, and portions
   thereof.

It should say:

   IMAP4rev1 includes operations for creating, deleting, and renaming
   mailboxes, checking for new messages, permanently removing messages,
   setting and clearing flags, RFC 5322 and RFC 2045 parsing, searching,
   and selective fetching of message attributes, texts, and portions
   thereof.

Notes:

RFC-3501 still refers to RFC-2822 which is obsoleted by RFC-5322. **One** example can be seen in the "Original text" section.
--VERIFIER NOTES--
Errata reports are for issues that were errors at the time of publication. RFC 5322 was published after RFC 3501, so RFC 2822 was the correct reference when RFC 3501 was published.

Report New Errata