Le 11/09/2024 à 10:16:21+1000, ellie timoney a écrit Hi, > > 3.0 is unable to sync mailboxes with annotations to 3.2 or later, for a few reasons (summarised below). See https://github.com/cyrusimap/cyrus-imapd/issues/4967 for full discussion. > > Brief summary: > 1) 3.0 doesn't send MODSEQ for ANNOTATION, but 3.2 and later require it > 2) 3.0 calculates SYNC_CRC_ANNOT differently (and incompatibly) from later versions > > Your mailboxes contain annotations due to having had conversations turned on. Turning conversations off does not remove the annotations. If you've turned conversations off already, you might be able to remove the annotations it created using IMAP SETANNOTATION, but I'm not sure exactly how. Removing the annotations should solve the problem. Ok. What append to my users on my current server if I disable «conversations» (currently enable) and remove all converations db ? Because I got some users (~ 3000) I don't want broke something. If I'm correct the conversations db is used to «sort» the messages. What's happen if I disable and remove all conversation db ? If I disable/delete conversation can I sync from 3.0 -> 3.2 -> 3.6 ? Can the conversations db be reconstruct in case of problem ? > > There's a patch linked in the github issue which should apply to 3.2, which makes it leniently accept the missing MODSEQ. With this patch, you might be able to sync a mailbox with annotations from 3.0 -> 3.2 without needing to remove the annotations first, if the mailbox doesn't exist on the replica yet. If you test this patch out, please post your results to the github issue. > > Once the mailbox exists on the replica, future attempts to sync that mailbox will definitely fail even with the patch, because the SYNC_CRC_ANNOTs won't match. I don't think it's possible to fix this in code. If you need to update the replica, you can remove the mailbox from the replica, and then replicate it in again from scratch. Ok. In that case I cannot do that. I've got ~ 3000 mailbox and ~ 30 To, and I cannot stop the service during few days to run one single sync. I need to be able to do a lot of sync to converge. > > You cannot upgrade directly from 3.0 -> 3.6, nor from 3.2.6 -> 3.6. To upgrade to 3.6, you must first upgrade to at least 3.2.10 or 3.4.4, run that and resolve any issues that arise, and then you can proceed. See https://www.cyrusimap.org/3.6/imap/download/upgrade.html#versions-to-upgrade-from > Ok. Thanks for the answer. -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: mer. 11 sept. 2024 10:32:23 CEST ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T99786d282b24ba9b-M4f7f0eb52efe8a05dde33bbd Delivery options: https://cyrus.topicbox.com/groups/info/subscription
