Displaying 2 results from an estimated 2 matches for "rfc4551".
Did you mean:
rfc4550
2015 Jul 19
1
RFC 5465 (NOTIFY) violation: missing HIGHESTMODSEQ in initial STATUS responses
...currently selected mailbox, and the client has specified
the STATUS indicator parameter, then the server MUST send a STATUS
response for that mailbox before NOTIFY's tagged OK. [?]
If either AnnotationChange or FlagChange are included and
the server also supports the CONDSTORE [RFC4551] and/or QRESYNC
[RFC5162] extensions, the STATUS response MUST contain UIDVALIDITY
and HIGHESTMODSEQ.? ?
https://tools.ietf.org/html/rfc5465#section-3.1
While unsolicited STATUS responses include HIGHESTMODSEQ indeed, the initial
STATUS responses (caused by the presence of the STATUS i...
2012 Apr 10
1
Bug in HIGHESTMODSEQ when MODSEQ tracking is not enabled for version 2.0.18.
...SEQ" or similar command, which appears to enable MODSEQ tracking at the server (according to the comment around line 173 in file src/lib-index/mail-index-modseq.c), but until that command is sent, MODSEQ tracking is not enabled and hence HIGHESTMODSEQ is always going to return 1.
According to RFC4551, the combination of HIGHESTMODSEQ and UIDVALIDITY should be sufficient to determine if the metadata associated with the mailbox has changed, but in this case looking at only those two parameters does not yield sufficient information about changes in the mailbox. The mail client I'm using relie...