I just upgraded from 2.4.17 to 3.0..3. My only troubles were with default options that changed, like the hierarchy separator, the namespace and delayed expunge. They all forced me to update scripts all around. And the namespace change had a nasty side effect: users must delete and add their accounts again (when using some mail clients) to restore order to the caos.
I could have kept the 2.4.x behavior, but I see the merit in the new defaults, so fixing scripts and having users refresh their account setup was worth it (not many users here). Hope you have more luck with 3.0.3. > On Aug 25, 2017, at 8:07 AM, Gabriele Bulfon <gbul...@sonicle.com> wrote: > > I will. > > Another note. > > I tried restarting from scratch, replicated my entire 2.4.12 system, checked > that it worked as expected, updated packages to 3.0.2 and started cyrus as is > with no upgrade : the problem is there just after updating the binaries, even > before migrating the data to the new version. > > I will absolutely try the 3.0.3, but I'm starting to feel unsafe > upgrading.... :( >
---- 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
