|  | Commit message (Collapse) | Author | Age | Files | 
|---|
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | Indeed we might get an untagged EXISTS response, meaning that a new
message has been received meanwhile. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | microsoft's IMAP server violates RFC 3501 by skipping the trailing space
for empty resp-text. | 
| | 
| 
| 
| 
| | We require QRESYNC support (RFC 7162) for syncing, which requires UID
(MODSEQ) in unsolicited FETCH responses, cf RFC 7162 section 3.2.4. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | RFC 3501:
    INBOX is case-insensitive.  All case variants of INBOX (e.g., "iNbOx") MUST
    be interpreted as INBOX not as an astring.  An astring which consists of
    the case-insensitive sequence "I" "N" "B" "O" "X" is considered to be INBOX
    and not an astring. | 
| | |  |