Re: Migration murder from 3.2 to 3.10 (Debian 11 to 13) – problems with shared folders
Frank Richter <[email protected]> Tue, 5 May 2026 15:45:25 +0200
| Newsgroups | gmane.mail.imap.cyrus |
|---|---|
| Message-ID | <[email protected]> |
Quoting Jean Charles Del=C3=A9pine via Info: > > Quoting Frank Richter <[email protected]>: > >> How does other admins of a Cyrus murder handle this, is anyone using=20 >> shared folders? We use it a lot for group scenarios, such as mailboxes=20 >> for project, departments etc. So for us the "pinning" of all group=20 >> folders to only one backend server isn't optimal. >> >> Would it be reasonable to have a configuration option for the namespace= =20 >> of shared mailboxes, so that for this name no mailbox will be created? > > imapd.conf options : > > =C2=A0 altnamespace: 1 > =C2=A0=C2=A0=C2=A0=C2=A0 Use the alternate IMAP namespace, where personal= folders reside at=20 > the same level in the hierarchy as INBOX. > > =C2=A0 sharedprefix: Shared Folders > =C2=A0=C2=A0=C2=A0=C2=A0 If using the alternate IMAP namespace, the prefi= x for the shared=20 > namespace.=C2=A0 The hierarchy delimiter will be automatically appended. > > I use altnamespace: 0 therfore my shared mbox are prefixed with "" : > > . NAMESPACE > * NAMESPACE (("INBOX." ".")) (("user." ".")) (("" "."))=20 The same here. > My folders are in INBOX.* > Other users folders are in user.* > Shared folders are all other folders. > > shared folders in my organisation are in general organised with '-', not = '.'.=20 That would solve it indeed. I=E2=80=99ll check it if this change would fit = to our needs. Thanks! --=20 Frank Richter, Chemnitz University of Technology, Germany ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Te7a1ee0606b2df5d-Mc6c4a1= 60c204cf6c8333d8a1 Delivery options: https://cyrus.topicbox.com/groups/info/subscription