Am 29.04.26 um 09:40 schrieb Frank Richter:
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.
How does other admins of a Cyrus murder handle this, is anyone using shared
folders? We use it a lot for group scenarios, such as mailboxes for project,
departments etc. So for us the "pinning" of all group folders to only one
backend server isn't optimal.
Would it be reasonable to have a configuration option for the namespace of
shared mailboxes, so that for this name no mailbox will be created?
Thanks,
Frank
--
Frank Richter, Chemnitz University of Technology, Germany
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/Te7a1ee0606b2df5d-Mf91dfae61179dff984bd124a
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
