RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 3516, "IMAP4 Binary Content Extension", April 2003

Note: This RFC has been updated by RFC 4466

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 3978
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Slusarz
Date Reported: 2014-04-29
Verifier Name: Nevil Brownlee
Date Verified: 2014-08-18

Section 4.3 says: 

If the domain of the decoded data is "8bit" and the data does
not contain the NUL octet, the server SHOULD return the data in
a <string> instead of a <literal8>; this allows the client to
determine if the "8bit" data contains the NUL octet without
having to explicitly scan the data stream for for NULs.

It should say:

If the domain of the decoded data is "8bit" and the data does
not contain the NUL octet, the server SHOULD return the data in
a <string> instead of a <literal8>; this allows the client to
determine if the "8bit" data contains the NUL octet without
having to explicitly scan the data stream for NULs.

Notes:

Typo: duplication of "for".

Status: Reported (1)

RFC 3516, "IMAP4 Binary Content Extension", April 2003

Note: This RFC has been updated by RFC 4466

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 8217
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Simon Ser
Date Reported: 2024-12-21

Section 7 says: 

   msg-att-static =/  "BINARY" section-binary SP (nstring / literal8)
                      / "BINARY.SIZE" section-binary SP number

It should say:

   msg-att-static =/  "BINARY" section-binary ["<" number ">"] SP (nstring / literal8)
                      / "BINARY.SIZE" section-binary SP number

Notes:

Section 4.3 describes the response as:

BINARY<section-binary>[<<number>>]

But the number is missing from the ABNF.

It seems like Dovecot sends the number in the response, and imaptest expects it.

Report New Errata



Advanced Search