On 26-Feb-2003 08:55 Andreas Aardal Hanssen wrote:
|
| Well, since the server trunk has to be compliant with standards, and there
| is only one way to store mailboxes and submailboxes in the
| Maildir/Maildir++ standards, I can't make it all configurable. The thought
The extension of Maildir into Maildir++ is a wholly courier-based idea
though adopted by other applications. I can't really say I think of
Maildir++ as a gold standard. Maildir is simply an object which handles
the (theoretically as intended anyway) reliable delivery of mail.
Certainly, uw-imapd can be/has been patched to support Maildir without
the baggage of Maildir++. The filesystem already provides a standard
way of supporting submailboxes.
| has struct me to make the maildir translation configurable through some
| sort of a scripting language, but that would mean that Binc allows
| noncompliant maildirs.
I'm presuming you mean "noncompliant Maildir++'s".
| Maildir is a mailbox format that consists of a directory on your harddrive
| with three subdirectories: cur, new and tmp, and some additional features
| that are all properly documented.
Some features are part of maildir proper (as per djb) and others
are extensions (Maildir++) made by Courier (any others?). Maildir
was designed for reliable mail delivery, while Maildir++ was designed
to extend (abuse) a Maildir to support an IMAP (+ other mail subsystems)
implementation.
| I think what you are looking for is support for mailbox formats other than
| Maildir, such as mbox, which allows a whole mailbox to be stored in one
| file alone. This server sadly doesn't support other formats than Maildir.
Nope. I want Maildir. I use Maildir for my mail delivery. I could
use it for archival purposes too, but I don't. I don't use Maildir++,
nor do I care for it. I'm already using an IMAP server that has been
patched to support Maildir (but not Maildir++). I deliver my mail
the way I want, structuring it as I please, within the confines of my
filesystem.
Maildir++ forces me to restructure my mail the way it wants, using
names I don't like, and polluting my Maildirs. Sure, I could
change all my mail folders to fit into the Maildir++ scheme, but
all my mail is already there, the way I like it, waiting for an
IMAP server to scoop it up. A patched uw-imapd doesn't have trouble
with this. I was hoping Binc wouldn't either. I really don't want
to run uw-imapd, but I'd rather it than use Maildir++.
| Yes, that's the general idea. The entire mailbox depository is inside one
| directory. This is usually considered to be a good thing, because the
| server can chroot("~/Maildir") and chdir("/"), reducing the total amount
| of damage done if a malicious user hijacked your IMAP session in some way
| or another.
You can chroot to any directory, so it doesn't have to be a Maildir++
directory. The way Binc works right now, it does a chroot(path), but
if path is not a Maildir, it's a no go. I understand your reasoning,
but my issue isn't that Binc does chroot(a directory), it's that it only
does chroot(a directory that must be a Maildir). You don't have to
sacrifice the goodness of chroot() by giving up on Maildir++. You
simply use a different (better?) restriction: chroot(a directory that
is a child of 'home'). Now you have an open playing field of directories,
which may or may not be Maildir/Maildir++.
--
-Dale
