On Fri, 21 Nov 2003, felix wrote: >BUT: The configuration shown above exposes the inbox as "." Instead of >being exposed as "." I'd rather have it exposed as something else, such >as "Inbox". ;-)
Ah, hehe. Okay here's a recap, lets see if I follow now. Well, the '.' is there because '.' qualifies as a Maildir. It's questionable wether Binc should test '.' for this property, and since it isn't really my intention I'd like to mark it as a bug. Now, excluding the presence of '.', you now have no inbox. :-) This is because the IMAPdir depot doesn't have that mailbox, or any symlink, which is a misconfiguration really. Usually the solution is to either create the symlink, or to instruct your MTA (qmail) to deliver to INBOX instead, or to switch to Maildir++. I believe is that your real problem is that Maildir++ forces you to create everything under INBOX, instead of giving you the option of creating everything _next_ to INBOX. Binc should support the last option, and through the NAMESPACE extension, this is very possible. Assuming that INBOX.INBOX is a reserved name that points to INBOX, setting the namespace INBOX would give you root level folders. This is somewhat how Courier-IMAP does it, and it's something Binc should support (we had a large discussion about these issues almost a year ago). With the NAMESPACE extension, users will not have to do anything to their setup, but with a fix to 1.2, users who define their IMAP namespace (in their client) to INBOX will probably achieve what you are wishing for. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
