On Mon, 17 Mar 2003, Andreas Aardal Hanssen wrote: > On Mon, 17 Mar 2003, Charlie Brady wrote: > >On Mon, 17 Mar 2003, Dan Mills wrote: > >'.' is the hierarchy separator. Although it isn't defined by RFC 2060, it > >makes sense to me that a leading hierarchy separator can be deleted - it > >isn't separating anything. Therefore .foo and foo are the same folder. > >This folder should always be .foo *or* foo in the file system storage. > >Which of these we choose depends, I think, on how compatible we wish to be > >with the paper definition of Maildir++. > > Here comes me with a constructed example again. If you have two mailboxes: > .foo and foo,
mailboxes, or maildirs in the file system? > and the client says "DELETE foo", which mailbox is > then deleted? > > What if the client then issues the same "DELETE foo" once more. Is the > second mailbox deleted? No. Please read what I wrote carefully. If '.' is the hierarchy separator, then foo and .foo are the same folder. They will be stored as *either* .foo *or* foo in the file system. Which ever it is, that maildir will be deleted when you first as for "foo" to be deleted, and will be not found the second time you ask. AIUI, Courier says that the maildir will be called ".foo". You will still have a maildir called "foo", but it will be irrelevant (invisible and untouched) as far as IMAP is concerned. Note that if '/' is the heirarchy separator, then "foo" and ".foo" are different folders. The Courier designated storage format will have these named as ".foo" and (presumably) "..foo", but IMO you'd be better off saying that ".foo" is an illegal folder name. -- Charlie
