wasm-demo/demo/ermis-f/imap-protocol/cur/1600095138.22911.mbox:2,S

36 lines
1.5 KiB
Plaintext

MBOX-Line: From mrc at CAC.Washington.EDU Mon Jun 25 09:49:11 2007
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc@CAC.Washington.EDU>
Date: Fri Jun 8 12:34:40 2018
Subject: [Imap-protocol] Namespace separators
In-Reply-To: <1182789432.3768.205.camel@hurina>
References: <1182783681.3768.187.camel@hurina>
<alpine.OSX.0.99.0706250816170.1955@pangtzu.panda.com>
<1182787190.3768.198.camel@hurina> <1182789432.3768.205.camel@hurina>
Message-ID: <alpine.OSX.0.99.0706250945200.1955@pangtzu.panda.com>
On Mon, 25 Jun 2007, Timo Sirainen wrote:
> Another question about weird namespace configurations:
> * NAMESPACE (("#mbox/" "/") ("#maildir." ".")) NIL NIL
>
> If LIST "" % returns nothing, should LIST "" "" return something? Or
> should some namespace always be assigned visible to root so LIST "" %
> works?
Since the empty namespace is the default namespace, LIST "" "" should
return something. INBOX is part of the default namespace, although it has
special semantics (in particular, case-independency).
In your example, I see not particular benefit to having both #mbox/ and
#maildir. . One or the other should be the default namespace. Actually,
AFAICT, both types of names can be in the default namespace as long as you
agree to use / as the hierarchy delimiter for maildir names; presumably
these names correspond to UNIX filesystem objects and not something else.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.