On Wed, 15 Aug 2001, Henning Brauer wrote:
> Why the heck make things such confusing? It is simple, the absolute path to
> the Maildir is
>
> (~/control/ldapmessagestore|"") . (mailMessageStore|HomeDirectory) .
> DefaultDelivery
>
> Why confusing things? Which requirement you have could not be reached this
> way?
>
To my mind, the way I've set it up is more natural for the way stock
qmail is set up (and the way courier authentication modules work, which
seems to be based on the same model). That is, there's a home directory
that the user owns (in the case of a virtual user, the virtual user owns
it), then there's some message storage location in that directory (either
an mbox or a maildir, depending on whether the location name ends in a /).
It's really a natural outgrowth of the fact that the originating process
is running as root, and the child process (that deals with the actual mail
storage) is running as the user.
I also think it makes a clearer mirror of .qmail files in ldap
attributes - there's one attribute that corresponds to .qmail lines
begining with '|', one that corresponds to '&', and this makes
mailmessagestore act like one beginning with '.' or '/' (although multiple
mailmessagestores aren't supported).
This also makes the naming make more sense to my mind. In particular,
"ldapmessagestore" seems to me to indicate a default mailmessagestore
(like the first argument to qmail-lspawn or imapd), rather than the root
mail directory.
Finally, the logic that was there just seemed excessive to me for what
should be a simple, straight computation. The qmail system was designed
to have these (the home directory, and the message store (mbox or
maildir)) separated out, why have all that in there? If mailmessagestore
is absolute, that would get changed to by the next process anyway.
But like I said, that part can always be thrown out. I don't have any
legacy to support for myself, so it was easy for me to just toss what was
there out because I didn't like it.
Lynn
