| Commit message (Collapse) | Author | Age | Files |
| |
|
|
|
|
|
|
| |
expunged
(before we had a chance to sync it)
|
|
|
|
|
|
|
|
|
|
|
| |
Indeed, if the server sends
* n EXISTS
* n EXPUNGE
meaning a new message is received, and is immediately removed
afterwards, the server might have allocated a new UID for the removed
message.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|