On pe, 2010-06-11 at 17:45 +0200, Thomas Hummel wrote: > On Fri, Jun 11, 2010 at 04:29:07PM +0100, Timo Sirainen wrote: > > > Yes. (But with hidden=yes it's not a client-visible namespace so it's > > ok.) > > So, if I do the combinatorics : > > a) hidden = no > list = no > > -> the "best" or "cleaner" way to define namespace since it rewards > clients which support NAMESPACE command ? > > > b) hidden = no > list = yes > > -> makes no sense to advertise a namespace which is always visible. > > c) hidden = yes > list = no > > -> setting up namespaces in client config is mandatory
Most commonly used for "compatibility namespaces", where client e.g. already has configured ~/mail/ prefix in UW-IMAP ages, and you want to have such namespace point to the default namespace. > d) hidden = yes > list = yes > > -> a setup where we don't want to support namespaces at all > > Correct ? Yes.
