> (Andreas Aardal Hanssen <[EMAIL PROTECTED]>): > > In Binc IMAP, all folders must be created as subfolders of INBOX. So > rather than creating "Foo", create "INBOX.Foo". > > Under INBOX, you can create subfolders and subsubfolders.
I think this needs to be rethought for bincimap to play better with others. I think many clients will allow the user to create mailboxes on the same level with "Inbox", and many people like to have their mail organized that way. Even if this isn't done, however, the mailboxes under Inbox should not have to be named with "." in the Unix filesystem for bincimap to find them. "INBOX.Foo" should be the directory "Foo" under ~/Maildir, not ".Foo". That's what mutt expects, for instance, when reading maildirs directly. Unix has a very old and very respected tradition that filnames and directories that begin with "." are hidden. So maildir clients like mutt won't look to see if such directories are maildirs. The whole point of using IMAP is to be able to read mail from many clients in many places under varying conditions, so it behooves the server not to make its own conventions for directories. At least with Maildir format there's a clear, simple, fool-proof test for what's a mail directory and what isn't: the existence of "new", "cur", and "tmp". We should take advantage of that to make the server flexible in where maildirs are located. >From a technical standpoint, "INBOX" is the tricky part. It appears from the code that the standard incoming maildir is the current directory of the server process (i.e., "."), so to find maildirs on the same level (say, by searching "../*") would require knowing what that directory was so it could be skipped. I could probably make this change to my local copy and test it for a while before suggesting my code be adopted; but I'd like to hear from others if they think it would be a good idea, or if the present system gets in their way as it does mine. -- Lee Daniel Crocker <[EMAIL PROTECTED]> <http://www.piclab.com/lee/> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC
