On Tue, 29 Mar 2022, at 12:36 AM, Andy Dorman wrote:
FWIW, I noticed most of our servers never added a uuid storage directorywhen they updated last weekend. Is there a setting I need to add inimapd.conf to enable uuid storage and use relocate_by_id to movemailboxes to it?
No, you don't need to do anything to enable uuid storage.
What might be confusing/surprising you is that no existing mailboxes are moved to uuid storage at all, until you relocate_by_id them. But new, top level mailboxes (e.g. new users) that you create after the upgrade are created in uuid storage. (This is why the create brand new mailboxes hierarchy -> copy files -> reconstruct trick worked.)
There is a new option "mailbox_legacy_dirs", which turns off uuid storage for newly created top level mailboxes only. That is, if you enable "mailbox_legacy_dirs", then any new top level mailboxes will be created in the legacy storage instead of the uuid storage. This still has no effect on existing mailboxes: existing mailboxes will remain wherever they were, and new submailboxes are always created wherever their parent is. You can always move mailboxes to uuid storage using relocate_by_id, regardless of your "mailbox_legacy_dirs" setting.
It's usual in Cyrus for directories to be created as they're needed, and not until. I don't know that this is definitely the case for the uuid directory, but it is consistent with how we usually do things. Given that you haven't created any new users since the upgrade, and the mailboxes that already existed will stay where they are until you relocate_by_id them, and any new mailboxes your existing users create will be in the same place as their existing ones, it is not surprising to me that there would not be a uuid directory yet on most of your servers.
Cheers,
ellie
