On Thu, 13 Mar 2003, Andreas Aardal Hanssen wrote:
> Everyone. Summing up some of the recent threads, how does this sound:
Excellent.
> 1) Maildir structuring for Binc IMAP changes.
...
> INBOX is obviously a special case here. Taking Dale's
> suggestions into consideration, if mail/ itself (or ~) is a
> Maildir, then this is used in place instead of INBOX and
> it's logged as a notice to the administrator because
> the mail/INBOX/ folder will then be ignored. The preferred scheme
> is to _not_ have mail/{cur,new,tmp} but mail/INBOX/{cur,new,tmp}.
>
> Typically, mail delivery (.qmail or rc or similar) must be
> instructed to deliver to the INBOX maildir in this new
> structure. Where this is not possible, a symlink from ~/mail/INBOX
> to ~/Maildir should do the trick.
I don't think this is necessary. INBOX location is a special case, and is
a local policy issue. It should be configured. I think that a command line
argument when the daemon is invoked is the way to go. My inbox is
~/Maildir, so I would have the daemon come to life as me (execed by the
authenticator) in my home directory, with a commandline argument of
"Maildir". No parsing to be done, and no ambiguity about where INBOX is.
(This is how qmail-pop3d works, no?)
[Why would "mail/INBOX/" be preferred to "Maildir/" for INBOX?]
I would then add a second command line argument which is the root of the
folder tree. In your example this would be "./mail/". That argument could
be optional, and would default to "./".
[Hmm, "./." or similar would clear up the Courier compatibility, wouldn't
it? No, we still have the flattened tree issue to deal with.]
> Comments please, comments! :-D
I'm in. Must dust off C++ skills. Let me know where I can help.
You haven't mentioned uidvalidity location. Inside each maildir?
--
Charlie
