2RFC 7162, "IMAP Extensions: Quick Flag Changes Resynchronization (CONDSTORE) and Quick Mailbox Resynchronization (QRESYNC)", May 2014
3Source of RFC: qresync (app)
4See Also: RFC 7162 w/ inline errata
9Publication Format(s) : TEXT
10Reported By: Dirkjan Ochtman
11Date Reported: 2017-06-28
12Verifier Name: Alexey Melnikov
13Date Verified: 2020-02-21
20 S: * OK [UNSEEN 12] Message 12 is first unseen
21 S: * OK [UIDVALIDITY 3857529045] UIDs valid
22 S: * OK [UIDNEXT 4392] Predicted next UID
23 S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
24 S: * OK [PERMANENTFLAGS (\Deleted \Seen \*)] Limited
25 S: * OK [HIGHESTMODSEQ 715194045007]
26 S: A142 OK [READ-WRITE] SELECT completed
32 S: * OK [UNSEEN 12] Message 12 is first unseen
33 S: * OK [UIDVALIDITY 3857529045] UIDs valid
34 S: * OK [UIDNEXT 4392] Predicted next UID
35 S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
36 S: * OK [PERMANENTFLAGS (\Deleted \Seen \*)] Limited
37 S: * OK [HIGHESTMODSEQ 715194045007] Ok
39 S: A142 OK [READ-WRITE] SELECT completed
43RFC 7162 purports to extend RFC 3501 by adding the HIGHESTMODSEQ value as an option for the resp-text-code syntax. However, RFC 3501 only uses resp-text-code in the resp-text ABNF production, in which case it is always followed by a single space ("SP") and the "text" non-terminal, which expands to "1*TEXT-CHAR", as in non-empty text. As such, having a response code without any human-readable text suffix is illegal per the RFC 3501 spec, and the examples should be updated to be correct.