<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi Adrien,<br></div><div><br></div><div>The replication upgrade path should be okay. In-place upgrades (that would use the affected reconstruct to bring mailboxes up to the same version as the server) would get bitten. Whereas if you replicate to a newer version server, the mailboxes on the replica will be created at the replica's preferred version already, so you don't need to reconstruct afterwards.<br></div><div><br></div><div>If you have messages that would theoretically be affected by this bug in 3.0, you won't be able to replicate them to 3.0 in the first place, because I think replication won't allow the 0 modseq. If this arises, I'm not sure how to recover from it and replicate the affected messages, since 2.4 and 2.5 won't alter the 0 modseq. If it can't replicate them, it will complain about it, so if you plan for the replication needing some handholding/restarting, you'll at least be able to identify which messages are broken in the process, and then figure out how to handle it once you know the size of the problem?<br></div><div><br></div><div>Another option, if you want to stick with the Debian packages, would be to skip 3.0.8 and install 3.0.11 from buster-backports (<a href="https://packages.debian.org/buster-backports/cyrus-imapd">https://packages.debian.org/buster-backports/cyrus-imapd</a>), and then you'll be immune to the problem. Though you still won't be able to replicate the affected messages to the new server, hmm.<br></div><div><br></div><div>Cheers,<br></div><div><br></div><div>ellie</div><div><br></div><div>On Thu, Sep 12, 2019, at 6:50 AM, Adrien Remillieux wrote:<br></div><blockquote type="cite" id="qt"><div dir="ltr"><div>Hello,<br></div><div><br></div><div>I have a server that I can't
update running cyrus 2.5.10 which contain mailboxes that have existed
from 2.3 and earlier (around 300Gb total). My plan is to update by
enabling replication with a new server running Debian Buster (so cyrus
3.0.8) and then shutting down the old server. There was a problem when
upgrading to 3.x.x with mailboxes created with cyrus 2.3 or before and
that was fixed in 3.0.11 (see <a href="https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html">https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html</a> and <a href="https://github.com/cyrusimap/cyrus-imapd/issues/2839">https://github.com/cyrusimap/cyrus-imapd/issues/2839</a> for the bug report)<br></div><div><br></div><div>Does
this upgrade path suffer from the same issue ? I am not familiar with
the inner-workings of cyrus. It appears that the Debian maintainers have
not backported the patch in 3.0.8 (see <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163</a> and I looked at the source code)<br></div><div><br></div><div>Cheers,<br></div><div>Adrien<br></div></div><div>----<br></div><div>Cyrus Home Page: http://www.cyrusimap.org/<br></div><div>List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/<br></div><div>To Unsubscribe:<br></div><div>https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus<br></div></blockquote><div><br></div></body></html>