On Sat, Jun 27, 2026 at 04:40:49PM -0700, Tyler via isync-devel wrote:
The server is RFC-compliant:
i doubt it.
rfc4551 section 1 says:
A client supporting CONDSTORE extension indicates its willingness to
receive mod-sequence updates in all untagged FETCH responses by
issuing:
[...]
This document uses the term "CONDSTORE-aware client" to refer to a
client that announces its willingness to receive mod-sequence updates
as described above.
it doesn't explicitly state that the server MUST NOT send anything
condstore-related otherwise, but it's kinda implied.
rfc7162 updates the extension, and its section 3.1 says:
A client supporting the CONDSTORE extension indicates its willingness
to receive mod-sequence updates in all untagged FETCH responses by
issuing one of the following, which are called "CONDSTORE enabling
commands":
[...]
Once a client issues a CONDSTORE enabling command, it has announced
itself as a "CONDSTORE-aware client".
this _still_ doesn't explicitly _forbid_ unsolicited condstore-related
behavior, but it tries _really_, _really_ hard to imply it. one has to
be particularly dense to not get the hint.
in summary, the server is simply broken. in fact, dovecot agreed last
time this has happened:
https://dovecot.org/list/dovecot-news/2014-October/000276.html
so please report the problem to the provider, and ask them to ensure
that upstream is aware of the issue if it's not due to a local
modification.
---
i would consider a workaround that generally discards unknown data items
(issuing a warning about it once per store), but i'll do that only if
the server isn't fixed soon.
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
