Hi Ellie i think I found the problem:
In in cyrus-imapd-3.4.8/imap/sync_support.c:1485 decode_annotationsthe 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 Quoting ellie timoney <[email protected]>:
Hi Michael, On Thu, 4 Jul 2024, at 12:15 AM, Michael Menge wrote:Hi Ellie, I was able to copy the failed mailbox to our test servers and I am still able to reproduce the error.Interesting, so that suggests it's something about that mailbox that's leading to the bad protocol talk. I wonder what?To me it seams that the failed command in the telemetry does only contain minimal sensitive data. If you want I can send the "APPLY MAILBOX" command directly to you.Please do, thanks. I'll see if I can figure out what the replica is complaining about, and maybe that will shed some light on the underlying cause.I will also try to debug it myself, but as we are sill in the process of migrating form 3.0 to 3.4 it may take some days,Sure, good luck. :) Cheers, ellie ------------------------------------------ Cyrus: InfoPermalink: https://cyrus.topicbox.com/groups/info/T8556e55b2133ffdf-M9344b2377a38533f17315b0aDelivery options: https://cyrus.topicbox.com/groups/info/subscription
-------------------------------------------------------------------------------- Michael Menge Tel.: (49) 7071 / 29-70316 Universität Tübingen Fax.: (49) 7071 / 29-5912Zentrum für Datenverarbeitung mail: [email protected]
Wächterstraße 76 72074 Tübingen
smime.p7s
Description: S/MIME-Signatur
------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T8556e55b2133ffdf-M7e8aaa1df3c771c094b4345b Delivery options: https://cyrus.topicbox.com/groups/info/subscription
