Re: cyrus sync errors from 3.0.18 -> 3.4.8-patched

Hi Michael,

That's interesting.  Does that mean that the mailboxes it was breaking on were just any mailboxes with annotations, and those mailboxes being DELETED.* was a coincidence?

I wonder if syncing from 3.0 -> 3.2 -> 3.4 would work.  Probably not, I assume 3.2 is also unable to accept annotations without modseq.  Unless it did for a while, and then that got broken.

Cheers,

ellie

On Tue, 9 Jul 2024, at 10:22 PM, Michael Menge wrote:
> Hi Ellie
>
> i think I found the problem:
>
> In in cyrus-imapd-3.4.8/imap/sync_support.c:1485 decode_annotations
> the sync server is expecting a MODSEQ for Annotations, but the older  
> version of
> cyrus did not send the MODSEQ
>
>
> It seems this feature was introduced between 3.0 and 3.2
>
> I have created a new Issue to track this
> https://github.com/cyrusimap/cyrus-imapd/issues/4967
>
> Kind Regards
>
>     Michael Menge

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T8556e55b2133ffdf-Me6715a9341b1c80fd2de38af
Delivery options: https://cyrus.topicbox.com/groups/info/subscription