namspace management
Hello,
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.
In fact there is no parent namespace
an no subscription management is possible at all.
On the other side I tried to change the PUBLIC namespace prefix to
"INBOX/PUBLIC" but now the namespace is
*below* the inbox. That's also not what I want.
How do other users organise the namespaces INBOX, PUBLIC, SHARED and
VIRTUAL (via virtual plugin) ?
Thanks Andreas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 12 Aug 2014, A. Schulze wrote:
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.
Did you tried:
location = maildir:/data/mail_public/Maildir/:INDEXPVT=~/.dovecot.index.public/:CONTROL=~/.dovecot.index.public/
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBU+sMrnz1H7kL/d9rAQLKLggAhnecLGjpAEPDRlUOlne+TArb8f0BVFuI 4Yi1I9t0LxTaaL89EV/ipnT36sqGXVYtlSYxXKAULpKHvSdhwg+4Em2sf5f86j8r tRnljbx+Wjh1ptLX46HsyByjhnTNQTJJQCP3IpU64xkUyzeWclZzqI3KrvX2Mkuj FZ8nZZin/p+Hz0YnFXML9ASARCx1cwYNI1BrbKI+foWXky0VLxK802jPpfZRplQw rHg8JdpsvzxV2R7IEu4986ovAtJ4LC2zx8u6TSQURFgYOC2SVI1SJYJt29wdCVp7 RP82elLsqGg5xaKpVZuU/7ueJg7ikGiE1qxpq6gFr9ZwjAZkYEjjAg== =K7ra -----END PGP SIGNATURE-----
On 13 Aug 2014, at 09:58, Steffen Kaiser <skdovecot@smail.inf.fh-brs.de> wrote:
location = maildir:/data/mail_public/Maildir/:INDEXPVT=~/.dovecot.index.public/:CONTROL=~/.dovecot.index.public/
Not recommended, because it also moves dovecot-keywords file so any keywords added to the public folder won't be shared across users.
Timo Sirainen:
On 13 Aug 2014, at 09:58, Steffen Kaiser
location =
maildir:/data/mail_public/Maildir/:INDEXPVT=~/.dovecot.index.public/:CONTROL=~/.dovecot.index.public/Not recommended, because it also moves dovecot-keywords file so any
keywords added to the public folder won't be shared across users.
OK, moved only the subscription file to a place next to the Maildir:
/data/mail_public/Maildir contain public mailboxes
/data/mail_public/Maildir/dovecot-acl allow access ( contain only
"authenticated lrs" )
/data/mail_public/subscriptions contain the subscription files
namespace {
inbox = yes
prefix = INBOX/
separator = /
}
namespace {
location =
maildir:/data/mail_public/Maildir/:INDEXPVT=~/.dovecot.public/:SUBSCRIPTIONS=../subscriptions/%Lu
prefix = PUBLIC/
separator = /
type = public
}
namespace {
list = children
location =
maildir:%%h/Maildir:INDEXPVT=~/.dovecot.shared/%%u/:CONTROL=~/.dovecot.shared/%%u/
prefix = SHARED/%%u/
separator = /
type = shared
}
Andreas
On 12 Aug 2014, at 19:04, A. Schulze <sca@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 }
participants (3)
-
A. Schulze
-
Steffen Kaiser
-
Timo Sirainen