Charlie Brady <[EMAIL PROTECTED]> writes: > I started this thread, so please allow me to reiterate my original > question - why can't I create a folder called "foo"?
[...] > Leaving aside for the moment the on-disk storage structure, does > Courier have this restriction - that one can only create folders > called "INBOX.xxx"? Have you read the Courier FAQ? In particular, http://www.inter7.com/courierimap/FAQ.html#namespace: I can't create any top-level folders, only subfolders of INBOX This is a configuration issue with your mail client. IMAP servers are free to use any folder namespace arrangement that's technically convenient for them. Courier-IMAP uses "INBOX." as the namespace for private folders, and "shared." as the namespace for public, shared, folders. The IMAP NAMESPACE extension (see http://www.rfc-editor.org/rfc/rfc2342.txt) allows IMAP clients to automatically discover where the server creates folders, and your IMAP client should implement it. This should be completely transparent to you, if your IMAP client properly uses the NAMESPACE extension. If your IMAP client were to automatically take advantage of self-configuration features offered by RFC 2060 and RFC 2342, it would automatically discover, without any additional configuration from the user, that: 1. The folder namespace hierarchy separator is the . character 2. Private folders are stored underneath the "INBOX." hierarchy 3. Public folders are stored underneath the "shared." hierarchy If you have to explicitly create folders that are subfolders of INBOX, or if you explicitly have to name that "INBOX.foldername", this is due to your IMAP client not being able to configure itself accordingly. So, is this whole argument an IMAP client configuration issue? Perhaps binc's storage structure doesn't need to be changed at all.
