[Dovecot] understanding namespace configuration
i'm a little confused about namespace configuration. reading http://wiki2.dovecot.org/Namespaces , and looking at the examples, it seems that when a namespace is declared, you can either do "namespace { ..." or "namespace foo { ..." - i'm having trouble finding clarity on the significance of "foo" though. it would appear it's not required, but then what is its purpose? what does it mean? does it imply something?
it's also unclear to me how to create the "default private namespace". i see that there are three types of namespaces, but the list of namespace settings doesn't seem to include a parameter to set the namespace type. what am i missing?
it's also not quite clear how to denote a namespace as "default". from coming across this thread [ http://mailman2.u.washington.edu/pipermail/imap-protocol/2010-May/001077.htm... ] it would indicate in theory that a namespace is denoted as default by using an empty prefix - but i wasn't able to find corroboration of that in dovecot's documentation.
thanks -ben
On 23.2.2013, at 18.26, btb@bitrate.net wrote:
i'm a little confused about namespace configuration. reading http://wiki2.dovecot.org/Namespaces , and looking at the examples, it seems that when a namespace is declared, you can either do "namespace { ..." or "namespace foo { ..." - i'm having trouble finding clarity on the significance of "foo" though. it would appear it's not required, but then what is its purpose? what does it mean? does it imply something?
It serves no other purpose than being able to refer to the namespace later in the config file.
it's also unclear to me how to create the "default private namespace". i see that there are three types of namespaces, but the list of namespace settings doesn't seem to include a parameter to set the namespace type. what am i missing?
namespace { type = private .. other settings .. }
They are private by default though. Also the wiki page was somewhat out of date .. I updated it now. It no longer talks about "default private namespace" at all, since it probably just adds confusion (especially with v2.1+).
it's also not quite clear how to denote a namespace as "default". from coming across this thread [ http://mailman2.u.washington.edu/pipermail/imap-protocol/2010-May/001077.htm... ] it would indicate in theory that a namespace is denoted as default by using an empty prefix - but i wasn't able to find corroboration of that in dovecot's documentation.
You don't need to.
On Feb 24, 2013, at 10.04, Timo Sirainen <tss@iki.fi> wrote:
On 23.2.2013, at 18.26, btb@bitrate.net wrote:
i'm a little confused about namespace configuration. reading http://wiki2.dovecot.org/Namespaces , and looking at the examples, it seems that when a namespace is declared, you can either do "namespace { ..." or "namespace foo { ..." - i'm having trouble finding clarity on the significance of "foo" though. it would appear it's not required, but then what is its purpose? what does it mean? does it imply something?
It serves no other purpose than being able to refer to the namespace later in the config file.
it's also unclear to me how to create the "default private namespace". i see that there are three types of namespaces, but the list of namespace settings doesn't seem to include a parameter to set the namespace type. what am i missing?
namespace { type = private .. other settings .. }
They are private by default though. Also the wiki page was somewhat out of date .. I updated it now. It no longer talks about "default private namespace" at all, since it probably just adds confusion (especially with v2.1+).
thanks, this fills in the missing pieces. are changes to the documentation wiki welcome from arbitrary folks in the community? i know it's a wiki, and get the essence and all that, but just wanted to ask out of consideration. i'd like to add a reference to "type =" in the list of namespace settings.
-ben
On 24.2.2013, at 21.25, btb@bitrate.net wrote:
are changes to the documentation wiki welcome from arbitrary folks in the community? i know it's a wiki, and get the essence and all that, but just wanted to ask out of consideration.
Anyone can change the wiki. I rarely revert changes entirely. But I do try to avoid having irrelevant things in there or explaining the same things in multiple different locations. If there is too much documentation people will stop reading it. :)
i'd like to add a reference to "type =" in the list of namespace settings.
I did some changes now related to that and other stuff.
participants (2)
-
btb＠bitrate.net
-
Timo Sirainen