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	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy	Date Submitted:
Summary Table Full Records

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

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

---

Errata ID: 3093
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Joe Pallas
Date Reported: 2012-01-18
Held for Document Update by: Pete Resnick

Section 6.3.11 says:

           Note: There MAY be exceptions, e.g., draft messages, in
           which required [RFC-2822] header lines are omitted in
           the message literal argument to APPEND.  The full
           implications of doing so MUST be understood and
           carefully weighed.

It should say:

           Note: There may be exceptions, e.g., draft messages, in
           which required [RFC-2822] header lines are omitted in
           the message literal argument to APPEND.  The full
           implications of doing so must be understood and
           carefully weighed.

Notes:

Possibly the result of a search-and-replace, these occurrences of "must" and "may" are not RFC 2119 usages.

Report New Errata