Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
Jean Charles Delépine écrivait (wrote) : > Hello, > > I'm on the way to migrate one quite big murder config with Cyrus IMAP > 3.0.8-Debian-3.0.8-6+deb10u4 > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1. > > My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work > before for 2.5 > to 3.0. migration. > > Il can replicate empty mailboxes. So the conf (attached) seems ok. > But if the mailbox isn't empty here's the result (completes traces attached) : The conf might not be _that_ ok. If the option conversation is set to 1 and I create new mailboxes, ond send mails to this mailboxes, no sync of these mailboxes is possible. If I remove the option 'conversation: 1', any new populated mailboxes can be sync. So, the problem seems to be in this option. But even after removing "conversation: 1" and zeroed conversation indexes (ctl_conversationsdb -z), the old "bad" mailboxes can't be synced. Even removing their .conversations and .counters files doesn't help. Can I, and how can I, get rid of those conversation indexes in order to have my mailboxes being "as if there never been conversation" ? Sincerly, Jean charles Delépine Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote: > Is this a known problem corrected after 3.0.9 ? Off the top of my head I no longer remember, but the current release in the 3.0 series is 3.0.14. I'd suggest, if you haven't already, that you look in the release notes from 3.0.8-3.0.14 and see if anything looks relevant. They're here: https://www.cyrusimap.org/imap/download/release-notes/3.0/index.html We don't generally recommend in-place upgrades between series (so, upgrading in-place from 3.0.8 to 3.2.3 is not something we'd recommend). Within-series, an in-place upgrade ought to be safe -- but please check the release notes carefully for extra steps/considerations you may need to make, depending on your deployment. I think you'll probably want to upgrade your 3.0 systems in place as far forward as you can (while staying 3.0), and then use the replication strategy to upgrade to 3.2 after that. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
