From: Noel Jones (no email)
Date: Mon Dec 01 2003 - 00:02:11 EST
On Mon, Dec 01, 2003 at 03:38:46AM +0100, Achim Altmann wrote:
>
> Yes, but i could find how can i configure over content_filter=
> but that isn't what i have to do
> I have now run postfix with amavisd-new over conten_filter but i have to
> transport some mails form a local domain without amavisd-new
> Yes i can config amavisd-new to bypass and so
> that isn't also that what can help me
>
Do you need to base your filter decision on the mail origin/sender
(client or insecure MAIL FROM) or by the destination/recipient?
Filter decisions based on recipient requires multiple instances of
postfix; the INPUT instance listens on port 25 and has transport table
entries to direct mail to either amavisd-new at 10024 or the postfix
OUTPUT instance at 10025. The content_filter directive is not used,
all routing is done with the transport table.
To configure multiple postfix instances, see the postfix INSTALL and
RELEASE_NOTES.
I would also recommend you get the multi-install support patch from
http://www.stahl.bau.tu-bs.de/~hildeb/postfix/duchovni/
While this patch is not required, it makes installing and maintaining
multiple instances much easier.
On the other hand, if you want to make filter decisions based on the
sender or client, you can use a normal amavisd-new+postfix
content_filter setup, and use and access table with the FILTER keyword
to bypass the content filter for selected mail.
If you are processing a mail list and wish it to bypass amavisd-new,
arrange for the MLM to submit mail to port 10025.
-- Noel Jones
|
|
|