Re: Patch (diff -u) for MAILDROP_README postfix-2.0.16-20031231

From: Wietse Venema (no email)
Date: Sun Feb 01 2004 - 09:47:56 EST


Thanks for the updated text. I will work it into the documentation.
The real issue isn't LDAP or not LDAP, however; it's deeper.

There are two approaches to hook a third-party delivery agent such
as maildrop into Postfix.

1) Indirectly via the Postfix local delivery agent. This gives you
the convenience of aliases(5) expansion and .forward processing.

    a) Specify "mailbox_command = /path/to/maildrop..." in main.cf.

Not relevant for Tonni's comments, but relevant in case people
want to host multiple domains:

    b) Specify "mailbox_transport = maildrop" in main.cf, and
       specify a maildrop configuration in master.cf. This gives
       all "mydestination" mail addresses (including accounts not
       in the passwd file) to maildrop.

    c) Specify "fallback_transport = maildrop" in main.cf, and
       specify a maildrop configuration in master.cf. This gives
       only the "mydestination" mail addresses non in the passwd
       file to maildrop.

2) Directly, without the Postfix local delivery agent. You get no
local aliases(5) expansion and no .forward processing, plus you
need to update main.cf with lists of valid recipient addresses.

    a) Specify a transport map that directs the domain in question
       to the maildrop configuration in master.cf. If the domain
       is in mydestination, update the local_recipient_maps in
       main.cf so Postfix smtpd does not reject all incoming mail.

    b) Specify "local_transport = maildrop" in main.cf, and define
       a maildrop configuration in master.cf. You also need to
       update the local_recipient_maps in main.cf so Postfix smtpd
       does not reject all incoming mail.

MAILDROP_README originally discussed variant (2) only. Tonni's
comments, on the other hand, are applicable to variant (1).

The old LMTP_README document mixed up variants (1) and (2). having
fixed that, I am now faced with an LMTP_README that is completely
at odds with VIRTUAL_README, and with a MAILDROP_README that gives
an incomplete account of the same things that LMTP_README discusses.
This still needs to be reconciled.

References:
    http://spike.porcupine.org/test/html/LMTP_README.html
    http://spike.porcupine.org/test/html/VIRTUAL_README.html

These are work in progress versions. I stil have to hyperlink
all the main.cf parameter definitions.

        Wietse








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD