On 10-Mar-2003 13:37 Charlie Brady wrote:
| 
| > >    1. Don't restrict the chroot() to a Maildir only.
| > >    2. Recommend use of a non-top-level Maildir scheme so that chroot()
| > >       can avoid top-level.  For example, recommend using ~/mail/Maildir
| > >       as the inbox & chroot ~/mail instead of ~/mail/Maildir.  Some
| > >       systems may wish to chroot ~/Maildir though.
| 
| "chroot" itself becomes problematic if you wish to have shared folders.

    Definitely.  How is bincimap supporting shared folders right now?

    I think the chroot() benefit only exists in limited circles, but
    the option is nice to have, especially if you want to support
    virtual users under a single uid/gid.

| > >    4. INBOX/hello refers to hello, hello/Maildir, hello/<Mailbox { path = ... }>,
| > >       or INBOX/.hello, whichever is the first Maildir
| > 
| > I like 4, it's the sort of design I'm looking for. This gives backwards 
| > compatibility while providing the features we want.
| 
| I think it would be wiser to have the local configuration fixed in a 
| config file than to try to guess local policy from the files and 
| directories which can be found.

    I agree, which I think was note (6) in my original post.  The layout
    may be different for each system/user, but it should be consistent
    for each.

| A directory is a maildir if it contains subdirectories tmp, new and cur. A
| maildir can contain other maildirs - even (if we are perverse) ones named
| tmp, new and cur. When you delete a maildir, you delete tmp, new and cur,
| and any messages contained therein, plus any additional administrative
| files we've added (uidvalidity, maildirfolder, maildirsize). If the
| directory is then empty, we delete it. Otherwise it stays, and is 
| reported by IMAP's list as \Noselect.

    This is good policy and doesn't restrict anyone to Maildir++.
    Depending on your reading of http://cr.yp.to/proto/maildir.html,
    maildir cannot contain other maildirs, and while I prefer having
    them opaque, I think the above addresses the issue.

    How do you propose dealing with non-folder/maildir subdirectories?
--
-dale

Reply via email to