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
