Tickets :: Comment on [#2874] Not prefixing with personal namespace

* Your Email Address
* Spam protection	Enter the letters below: ..__ . ..__..__ \|[ __\| \|[__][__) \__\|[_./\|/\\|\| \|\| \
Comment	>>> So this is happening because cyrus must have a private or public > >>> namespace defined that is empty (i.e. ''). Fixing this by always > >>> using the default namespace won't work because then it is impossible > >>> to create folders in an empty namespace. > >> > >> No, because we already agreed that users can only create mailboxes > >> inside existing shared mailboxes. And shared mailboxes are the empty > >> ones on Cyrus, and you can create new folders inside of them by > >> ticking the corresponding shared parent mailbox. > > > > Sound like i didn't explain myself well enough. > > > > Imagine I am using the brand new foo IMAP server. I configure it as follows: > > personal namespace = 'INBOX.' > > shared namespace = '' > > > > I have 1 mailbox in the INBOX namespace named 'foo1'. I have 1 > mailbox in the shared namespace named 'foo2'. > > > > Therefore, my folder hierarchy looks like: > > > > INBOX > > foo1 > > foo2 > > > > Q: how do i create a new mailbox in the empty namespace? A: I can't. > Trying to create a folder without checking a box will create the > folder under 'INBOX.'. > > > > As mentioned below, we could go back to the old way of displaying > items which would result in a display like the following: > > INBOX > > foo1 > > foo2 > > > > But this has the horrible effect of causing all new folders to be > created when no mailboxes are checked in the shared namespace, not > the personal namespace (which is probably not what either the user > nor the admin wants). > > > > As stated previously, I think the solution in this case is requiring > a confirmation screen in the case where there is a non-default > namespace that is the empty string.
Attachment
Watch this ticket

Saved Queries