On 26-Feb-2003 08:14 Andreas Aardal Hanssen wrote:
|
Thanks for the response Andreas.
| But you are free to make this change yourself, or with help from the
| community. I seems there are quite many preferences on this topic. :-)
Hmm, yes. I gather this from what I've read in the archives.
| I'm tempted to isolate the code that transforms IMAP mailbox names to
| Maildir paths further, simply for the purpose of making changes like this
| easier.
Wouldn't you say this is just one step (or several tiny ones) away
from having support for a transformation definition in the config?
And isn't that just one (...) step away from having a completely
open scheme?
Either way, that would be a most welcome change.
That the server will chroot to the mail path is nice, but it would
be nicer still if it was not strictly required for the mail path to
be a maildir. For example, one might want all mail to sit under
~/mail/. The inbox might be ~/mail/INBOX or ~/mail/Maildir.
Naturally the name is irrelevant as long as inbox is actually
a maildir.
I guess the issue (for me) is that Binc is taking advantage of
the fact that a Maildir is a directory; it can chroot to this
directory, but that makes namespaces harder to deal with.
I prefer to think of a Maildir as a blackbox, with some parts
of the system understanding the internals and others not. In
this case, "where your mail lives" (a path) should not penetrate
the black box, whereas "is this a valid mailbox" should.
With Binc taking advantage of "a Maildir is a directory" via
chroot, it sort of paints itself into a corner by requiring
other mailboxes to also be inside that Maildir (the black box).
regards.
--
-Dale
pgp00000.pgp
Description: PGP signature
