RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (2)

RFC 4469, "Internet Message Access Protocol (IMAP) CATENATE Extension", April 2006

Source of RFC: lemonade (app)

Errata ID: 2002

Status: Verified
Type: Technical

Reported By: Mike Abbott
Date Reported: 2010-01-14
Verifier Name: Alexey Melnikov
Date Verified: 2010-04-02

Section 5 says:

   url-resp-text = 1*(%x01-09 /
                      %x0B-0C /
                      %x0E-5B /
                      %x5D-FE) ; Any TEXT-CHAR except "]"

It should say:

   url-resp-text = 1*(%x01-09 /
                      %x0B-0C /
                      %x0E-5C /
                      %x5E-FE) ; Any TEXT-CHAR except "]"

Notes:

The skipped character %x5C is "\" not "]". I think the intent is to omit "]" since url-resp-text is used exclusively inside a [BADURL url-resp-text] response code, and they want to avoid aliasing the closing "]".

Errata ID: 4046

Status: Verified
Type: Technical

Reported By: Chris Newman
Date Reported: 2014-07-10
Verifier Name: Barry Leiba
Date Verified: 2014-07-10

Section Appendix A says:

   S: A003 NO [BADURL "/INBOX;UIDVALIDITY=785799047/;UID=113330;
   section=1.5.9"] CATENATE append has failed, one message expunged

It should say:

   S: A003 NO [BADURL /INBOX;UIDVALIDITY=785799047/;UID=113330;
   section=1.5.9] CATENATE append has failed, one message expunged

Notes:

This example treats the url-resp-text in the badurl-response-code as though it were an astring. It is not: it is a bare imapurl, as stated in section 5:

"The astring in the definition of url and the url-resp-text in the
definition of badurl-response-code each contain an imapurl as defined
by [2]."

The example is incorrect, in that the double quotes should be removed so the url-resp-text is a valid imapurl, and only that.

Report New Errata