MBOX-Line: From tss at iki.fi  Mon Jun 25 08:59:50 2007
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:40 2018
Subject: [Imap-protocol] Namespace separators
In-Reply-To: <alpine.OSX.0.99.0706250816170.1955@pangtzu.panda.com>
References: <1182783681.3768.187.camel@hurina>
	<alpine.OSX.0.99.0706250816170.1955@pangtzu.panda.com>
Message-ID: <1182787190.3768.198.camel@hurina>

On Mon, 2007-06-25 at 08:29 -0700, Mark Crispin wrote:
> Simple answer: this is why we have the # convention for alternative 
> namespaces, especially those which change the hierarchy delimiter.

I find this # thing also a bit weird. The client can't know about those
namespaces without NAMESPACE command, and if it does then there's really
no need for # because it can find out the exact prefixes anyway. So why
should the client do anything differently if there's #?

> Let me emphasize this: only ONE namespace is listed in a LIST command 
> command.  Namespaces are NOT the same as root level names.  By defining a 
> separate namespace you declare those names to be OUTSIDE of the space 
> listed in other namespaces!!!

I've understood that many commonly used clients ignore namespaces and
only show what is visible with LIST "" *, so I'd want to keep it
possible to list contents of all namespaces with it.

Dovecot actually allows the admin to configure any kind of namespaces.
I'm currently just wondering what kind of configurations I should
prevent.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20070625/65a16add/attachment.sig>
