MBOX-Line: From murch at andrew.cmu.edu  Tue Feb 28 05:46:58 2006
To: imap-protocol@u.washington.edu
From: Ken Murchison <murch@andrew.cmu.edu>
Date: Fri Jun  8 12:34:36 2018
Subject: [Imap-protocol] Re: Superior hierarchical mailbox creation....
In-Reply-To: <fbe19dd00602280135r570f4946ofe29a42707fdc815@mail.gmail.com>
References: <fbe19dd00602280135r570f4946ofe29a42707fdc815@mail.gmail.com>
Message-ID: <44045452.2050407@andrew.cmu.edu>

nikhil BS wrote:
> Hi all,
> We are developing a client for IMAP server.
> I tried to create mailbox of the form x.y.z where '.' is the heirarchy 
> separator.
> According to the RFC,
> 
> --
> If the server's hierarchy separator character appears elsewhere in
>       the name, the server SHOULD create any superior hierarchical names
>       that are needed for the CREATE command to be successfully
>       completed.  In other words, an attempt to create "foo/bar/zap" on
>       a server in which "/" is the hierarchy separator character SHOULD
>       create foo/ and foo/bar/ if they do not already exist
> --
> 
> But the mailbox x.y.z was created and not the superior hierarchical 
> mailboxes x, x.y weren't.
> This is the output of the LIST command...

The text in RFC 3501 says that the server SHOULD create any superior 
*hierarchical names*, which Cyrus does.  It doesn't say that it must 
create the hierarchical mailboxes.  I believe that Cyrus is and has been 
compliant in this regard.

I've CC'd this to the IMAP protocol list to see if others agree/disagree.

-- 
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University

