On Thursday, July 18, 2024, at 12:10 PM, Nic Bernstein wrote:
> This is covered in the documentation, but, sadly, the pertinent
section
<https://www.cyrusimap.org/imap/download/upgrade.html#upgrading-to-3-8> has
been labeled "Upgrading to 3.8" when it really
applies to several generations of upgrades.
>
> Please check that link, and especially part 5, "Copy config files
and update."
I followed all those instructions. All applicable steps were performed,
including the *reconstruct -V max*. I suspect our problem is somehow related
to the fact that we run with *altnamespace: off* and the default for that has
changed to *on*. Not knowing anything about the code, it feels like something
else was broken when that default was changed. As I mentioned in another reply
to Simon, when I briefly changed that setting to *on*, our email clients could
suddenly see the sub-folders that could not be seen before (because
"\HasNoChildren" had been changed to "\HasChildren"), but the view of the
*INBOX* was changed somehow. In some cases, a physical new *INBOX* folder was
created in */var/spool/imap/user/<user>* location (Thunderbird might have
caused this in response to the change), and any clients attempting to access
previously-known folders during this period all failed. I had to quickly
change the setting back, but then some mailboxes had to be repaired and the new
extraneous *INBOX* folders had to be deleted with *cyradm*. Not a good
situation.
I'm still stuck in the same situation I was in when I posted. Why is "*. LIST
"" **" no longer reporting that *INBOX* "\HasChildren" like it was with the old
version?
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/T8814f078026d7b10-Mf43fd1308d1b7967a18d8ede
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
