Le 11/05/2026 à 11:16:31+0200, Per olof Ljungmark a écrit Hi, > Trying for the Nth. time to upgrade from 3.0.18 to newer (3.2.12 currently) > version using sync, the plan is to increment upgrade to 3.4 and so on. > > It is a very standard setup, no murder etc., around 500GB mailstore, 100+ > accounts.. > > Switched from Xapian to Squatter > Disabled and removed conversations (-z) > Restarted imapd > > Replication runs fine for about 2/3 of the accounts, then bails out. > > Ran all sorts of reconstruct on the specific mailbox, checked telemetry etc > etc nothing helps. > > Debugging Cyrus IMAP is not exactly a walk in the park, how can I find what > is wrong with this specific account? > > sync_client -vv -l dumps a LOT of info but where in there do I see the > problem?
I wouldn't answer your question about what append because I've no clue. All I can say is I made the upgrade from 3.0.something on Freebsd to 3.6.1 on Debian with imapsync. It's a little painful but work fine. The first time of the sync is long (don't remember exactly but it's around 12 h). The last sync (no service) is around 1 h for ~ 100 000 mailbox ~ 10To. And in this 1h, 90% is for one mailbox who is a little «crazy» with one mailbox of 250 000 mails. Because the imapsync is working with the imap protocol I'm «sure» everything is create as it should be on the new server. I'm write some basic script to sync the acl. Same thing with sieve. Regards -- Albert SHIH 🦫 🐸 France Heure locale/Local time: lun. 11 mai 2026 11:19:53 CEST ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T32de718f28fc5421-M21ddb490e244e86febdd4f28 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
