Hi Michael, > Which Cyrus Version did you use before. I am nur using debian for my mailservers so i don't know if the upgrade of distribution did all the cyrus upgrade steps See https://www.cyrusimap.org/3.6/imap/download/upgrade.html for details.
yes, it's mainly a debian issue. I was coming from 3.2.6-2+deb11u2 and accoding to the link you posted, I should have upgraded to 3.2.10+ first, then make sure that the "inconsistencies in their storage of an optional metadata field (mailbox uniqueids). This was not previously a problem due to the field being optional." are fixed, and then upgrade to 3.6. But the debian release notes were not telling, that it *will* break for sure, if you have older mailboxes on your server (in my case being created with cyrus 2.6). It was not telling anything about any breaking change, even if there are already bugs filed. On the other hand, if with 3.6, some metadata is mandatory nowerdays, why is there not a tool available generating these IDs. Why is in reconstruct the comment in the code: metadata mandatory, so what could go wrong. Next line de-referencing a null pointer. Hey that's not how a recovery tool should work, right? Other example: "mbentry has no uniqueid, needs reconstruct" - but reconstruct cannot do that... And the comment at https://fossies.org/linux/cyrus-imapd/imap/mbpath.c in line 258 made me wonder, why I get the error message, having legacy mailboxes without ID. > has the debian package installer/upgrade moved your mailboxs.db and replayed it with an empty one, or have the paths changed? I don't know what exactly went wrong. I assume, that after first start, the mailbox.db was migrated to the new version but this broke due to many missing uniqueids. So I was ending without any mailboxes.db. That why even ctl_mboxlist Dump imported via -Legacy was not working. Because the IDs were still missing. And again, my fault. But cyrus had no recovery path available. If a legacy mailbox.db-import is available, it should generate missing IDs during import, right? Looking at https://packages.debian.org/search?keywords=cyrus-common&searchon=names&suite=all§ion=all there is no upgrade path at Debian but compiling your own version. And that's nothing I want to do in production. --Chris ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/Tc0e863bae9053445-M49a428813ebbbf08a1783d3d Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
