From: (no name) (no email)
Date: Sun Feb 01 2004 - 10:33:48 EST
On Sun, 1 Feb 2004, Tony Earnshaw wrote:
> +LDAP and maildrop.
> +
> +maildrop can be compiled with LDAP support by including "--enable-maildropldap"
> +in the configure parameters.
> +
> +maildrop's LDAP support, combined with Courier IMAP's authldap.schema, give 3
> +new objectclasses over and above standard object classes. These enable LDAP-
> +based quotas, virtual aliases and virtual mailboxes, as well as maintaining
> +regular $HOME/Maildir based mail directories, where these are applicable.
> +
This is not about LDAP at all! You are confusing LDAP (which you are using
for *your* local user database) with the more general possibility of using
maildrop for delivering mail to UNIX users (or perhaps even non-UNIX user
localpart addresses in local domains).
> +By using the standard combination of master.cf/transport as given above,
> +NO standard Postfix LDAP lookups are done before passing the message to the
> +Postfix transport. This in itself takes care of immediate delivery; however, it's
> +most likely that LDAP lookups have to be done - for example on system and other
> +aliases - before enabling delivery to users' mailboxes.
> +
There is no such thing as a standard Postfix LDAP lookup. There is however
alias expansion in the local delivery agent which uses LDAP if that is
what the administrator chooses to use for alias expansion, but LDAP is not
the point. Once more LDAP is irrelevant in this context, you use LDAP for
alias expansions, others use Berkeley DB or MySQL...
> With Postfix 2.1.0 (perhaps before that too), it is possible to
> circumvent the master.cf/transport pair by giving maildrop as the
> mailbox_command in main.cf and omitting the master.cf/transport
> combination. Choosing this alternative enables all LDAP lookups before
> passing the message to the transport. For LDAP deliveries, the file
> /etc/maildropldap.config has to be configured correctly before this will
> work.
>
Support for mailbox_command is considerably older, predating 1.0 by 3
years...
19980214
Feature: local delivery to configurable system-wide command
(e.g. procmail) avoids the need for per-user ~/.forward
shell commands. Config parameter: mailbox_command.
The similar mailbox_transport feature was added a year later, and is
useful when maildrop needs to run with its own uid/gid rather than as the
user.
19990314
Feature: "mailbox_transport = cyrus" delegates all local
mailbox delivery to a master.cf entry called "cyrus" (the
same trick for procmail), including users not found in the
UNIX passwd database. This gives the flexibility of $name
expansions by the pipe mailer, without losing local aliases
and ~/.forward processing. Result of discussions with Rupa
Schomaker, RS Consulting.
mailbox_transport takes precedence over mailbox_command, and both are
described in sample-local.cf and local(8).
I really don't think that this material belongs in MAILDROP_README per-se,
it is true for any alternative final delivery agent. A simple reference
from MAILDROP_README to a common document describing custom LDA/VDA
integration will suffice.
-- Viktor.
|
|
|