namspace management

[Timo Sirainen]

On 12 Aug 2014, at 19:04, A. Schulze <sca at andreasschulze.de> wrote:

> since some weeks I'm playing with namespaces. But I still did nod found a solution for all faces of different problems.
> 
> Current issue: Public namespace.
> I have users inbox as follow:
> 
> mail_home = /data/mail/%Ln/
> mail_location = maildir:~/Maildir:INDEX=~/.dovecot.index
> namespace {
>  inbox = yes
>  separator = /
>  prefix = INBOX/
> }
> 
> Public namespace:
> namespace {
>  location = maildir:/data/mail_public/Maildir/:INDEXPVT=~/.dovecot.index.public/
>  prefix = PUBLIC/
>  separator = /
>  type = public
> }
> 
> that way only one subscription file is possible. Any use could subscribe/unsubscribe any folder
> and that match all users.
> If I add "subscription=no" the parent namespace' subscription is used.

This is the solution.

> In fact there is no parent namespace an no subscription management is possible at all.

Add another namespace just for the subscriptions:

namespace {
  list = no
  hidden = yes
}