From: Timo Sirainen Date: Fri, 5 Dec 2008 19:16:15 +0000 (+0200) Subject: Updated comment about shared namespaces. X-Git-Tag: 1.2.alpha5~40 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0eebc3fdcdd92fa1c3202eaf2a7eee93017fc7ef;p=thirdparty%2Fdovecot%2Fcore.git Updated comment about shared namespaces. --HG-- branch : HEAD --- diff --git a/dovecot-example.conf b/dovecot-example.conf index 1960bfa899..a03a9ed40a 100644 --- a/dovecot-example.conf +++ b/dovecot-example.conf @@ -224,11 +224,13 @@ # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections. # -# You can have private, shared and public namespaces. The only difference -# between them is how Dovecot announces them to client via NAMESPACE -# extension. Shared namespaces are meant for user-owned mailboxes which are -# shared to other users, while public namespaces are for more globally -# accessible mailboxes. +# You can have private, shared and public namespaces. Private namespaces +# are for user's personal mails. Shared namespaces are for accessing other +# users' mailboxes that have been shared. Public namespaces are for shared +# mailboxes that are managed by sysadmin. If you create any shared or public +# namespaces you'll typically want to enable ACL plugin also, otherwise all +# users can access all the shared mailboxes, assuming they have permissions +# on filesystem level to do so. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. mail_location does nothing unless you have a namespace