Re: Migration murder from 3.2 to 3.10 (Debian 11 to 13) – problems with shared folders

Quoting Jean Charles Delépine:
>
> Quoting Frank Richter <[email protected]>:
>
>> We’re facing a problem with shared folders. Our shared folders have this 
>> scheme:  "group.sub.name"
>> The problem occurs when creating a new shared folder 
>> "group.sub.othername" on backend "packet":
>>
>> 2026-04-28T12:57:40.824198+02:00 packet cyrus/imaps[2647805]: MUPDATE: 
>> can't commit mailbox entry for 'group'
>> 2026-04-28T12:57:40.828960+02:00 packet cyrus/imaps[2647805]: Fatal 
>> error: Internal error: assertion failed: imap/imapd.c: 1494: 
>> !open_mailboxes_exist()
>>
>> Hm, "group" shouldn’t be a mailbox, at least it wasn't on cyrus-imapd 
>> 3.2.11. But now there is :
>
> In the Cyrus IMAP 3.6 Releases you will find :
>
> Major changes since the 3.4 series
>
>     All members of a newly created mailbox hierarchy will now be 
> selectable mailboxes. In other words, when creating mailbox 
> user.foo.A.B.C, both user.foo.A and user.foo.A.B will also be created as 
> real mailboxes. 
I read this … and hoped that this is the case only for user.* mailboxes.
Now in my setup this means that I can’t distribute my shared folders group.* 
between backends any longer – all group mailboxes have to be on the same 
backend server now. This hurts (a bit). If this would be the same for user 
mailboxes, then a murder setup makes nearly no sense.

Thanks,
Frank

-- 
Frank Richter
Facharbeitsgruppe Datenkommunikation
Universitätsrechenzentrum

Technische Universität Chemnitz
Straße der Nationen 62 | R. A11.302.1
09111 Chemnitz
Germany

Tel: +49 371 531 31879
[email protected]
www.tu-chemnitz.de/urz


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Te7a1ee0606b2df5d-M86a1c3cd3c89bce70344a2f5
Delivery options: https://cyrus.topicbox.com/groups/info/subscription