dovecot-1.2: Updated comment about shared namespaces.

[dovecot at dovecot.org]

details:   http://hg.dovecot.org/dovecot-1.2/rev/101b206caa00
changeset: 8516:101b206caa00
user:      Timo Sirainen <tss at iki.fi>
date:      Fri Dec 05 21:16:15 2008 +0200
description:
Updated comment about shared namespaces.

diffstat:

1 file changed, 7 insertions(+), 5 deletions(-)
dovecot-example.conf |   12 +++++++-----

diffs (22 lines):

diff -r 3dc481f92b7d -r 101b206caa00 dovecot-example.conf
--- a/dovecot-example.conf	Fri Dec 05 21:13:13 2008 +0200
+++ b/dovecot-example.conf	Fri Dec 05 21:16:15 2008 +0200
@@ -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