errata logo graphic

Found 1 record.

Status: Verified (1)

RFC6855, "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: 2014-07-01

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 a charset
   label and associated strings in the command arguments. Such
   extensions presently include SORT, THREAD and MULTISEARCH.

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