errata logo graphic

RFC5162, "IMAP4 Extensions for Quick Mailbox Resynchronization", March 2008

Note: This RFC has been obsoleted by RFC7162

Source of RFC: lemonade (app)

Errata ID: 1365

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-03-11
Held for Document Update by: Pete Resnick

Section 1. (ff.) says:

   A client making use of this extension MUST issue "ENABLE QRESYNC"
   once it is authenticated.  A server MUST respond with a tagged BAD
   response if the QRESYNC parameter to the SELECT/EXAMINE command or
   the VANISHED UID FETCH modifier is specified and the client hasn't
   issued "ENABLE QRESYNC" in the current connection.

It should say:

   A client making use of this extension MUST issue "ENABLE QRESYNC"
   once it is authenticated.  A server MUST respond with a tagged BAD
   response if the QRESYNC parameter to the SELECT/EXAMINE command or
   the VANISHED UID FETCH modifier is specified and the client hasn't
|  issued "ENABLE QRESYNC", or the server has not positively responded
|  to that command with "ENABLED QRESYNC", in the current connection.

Notes:

Rationale:
According to RFC 5161, the option enablement handshake is only
complete, and hence the option(s) enabled on the server, if the
server has sent a positive (untagged) "ENABLED <option>" response
to the ENABLE command.
For clarity, RFC 5162 should unambiguously reflect this causality
chain.

This same issue recurs in Section 3.1 (last paragraph on page 4)
and Section 3.6 (4th paragraph on page 13).


Report New Errata