On 03/03/2026 14:12, Frank Richter wrote: > Oh dear, thanks for pointing out this one. No, we don’t > use improved_mboxlist_sort: 1 yet
Keep in mind that you need to stop cyrus on all backends, export the mailboxes.db, change the setting and reimport the dump to a fresh mailboxes.db. After doing so you should do a "ctl_mboxlist -m" to a clean/empty mailboxes.db on your mupdate master after you changed the setting there as well. Last but not least change the setting on the frontends and fetch a new copy from mupdate there as well. Take note of #5593 on github and keep lmtp silent in the time of first sync. So you need a downtime. Depending on the size of your backends, primarily the mailboxes.db entry count, the "ctl_mboxlist -m" can take quite some time. > … Another question: We use DIGEST-MD5 to > authenticate to the mupdate master, too. > What shall I use instead? PLAIN requires TLS, right? > But mupdate doesn't support TLS according to https://github.com/cyrusimap/ > cyrus-imapd/issues/2774 > What do you use instead? Anything newer and (more) secure cyrus-sasl supports. eg. SCRAM-SHA-256. I also recommend scanning the currently open issues on github. There are some which will hurt big time if applicable and unaddressed. eg: #5548 We did the 2.5 => 3.8 migration in place BTW. We did a lot of "pre flight tests" and there were some lessons to learn, but aside from improved_mailboxlist_sort nothing we couldn't handle after the upgrade since we build our own RPMs with local patches for open issues. By using plain debian builds YMMV in a murder env;-) Greetings, Wolfgang -- Wolfgang Breyha <[email protected]> | https://www.blafasel.at/ Vienna University Computer Center | Austria ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Tc654c39c5afc4bc1-M897c6aa550f3719c55b28852 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
