RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Verified (1)

RFC 6855, "IMAP Support for UTF-8", March 2013

Source of RFC: eai (app)

Errata ID: 4029

Status: Verified
Type: Technical

Reported By: Chris Newman
Date Reported: 2014-06-27
Verifier Name: Barry Leiba
Date Verified: 2016-02-23

Section 3 says:

   Once an IMAP client has enabled UTF-8 support with the "ENABLE
   UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
   contains a charset specification.  If an IMAP server receives such a
   "SEARCH" command in that situation, it SHOULD reject the command with
   a "BAD" response (due to the conflicting charset labels).

It should say:

   Once an IMAP client has enabled UTF-8 support with the "ENABLE
   UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
   contains a charset specification. If an IMAP server receives such a
   "SEARCH" command in that situation, it SHOULD reject the command with
   a "BAD" response (due to the conflicting charset labels). This also
   applies to any IMAP command or extension that includes an optional
   charset label and associated strings in the command arguments,
   including the MULTISEARCH extension. For commands with a mandatory
   charset field, such as SORT and THREAD, servers SHOULD reject charset
   values other than UTF-8 with a “BAD” response (due to the conflicting
   charset labels).

Notes:

This is a straightforward extrapolation of the existing text, but a literal reading of the existing text is silent about how to deal with this situation.

Report New Errata



Search RFCs
Advanced Search
×