From: Achim Altmann (no email)
Date: Mon Dec 01 2003 - 07:32:27 EST
Hello,
Noel Jones schrieb:
>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?
>
destination/recipient
But the problem is the second amavisd-new-scan (like content_filter)
This overwrite the x-original-to:
The Problem is:
some mails com from to
.
And gous trought content_filter like amavisd-new. That's fine and what i
like.
The user have an sieve-filter (cyrus-timesieved)
and say
if a mail com from the
forward this mail to (this account
have an catch_all entry) and without conetnt_filter stands in my
mailheader the entry
x-original-to:
That is it what i need
With content_filter stand not
x-original-to: 1834_internal at sms
in mailheader
than is x-original-to:
and this is my problem
i have had also tested with
receive_override_options=no_unknown_recipient_checks,no_header_body_checks,no_address_mappings
but that couldn't clear this problem
The problem is the second way trough the content_filter
this rewrite my x-original-to:
Now ralf Hildebrand said i have to clear that over differend
transport-methods
over transport_maps
like
all what go to @sms.in transport this mails only over smtp and without
content_filter and the rest trough the normal-way content_filter like
amavisd-new
>
>Filter decisions based on recipient requires multiple instances of
>postfix;
>
If is this so if you have read above, please answer my short.
>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.
>
>
Sorry, no that i have tested an the problem is the second way trought
content_filter
bypass couldn't clear that
>If you are processing a mail list and wish it to bypass amavisd-new,
>arrange for the MLM to submit mail to port 10025.
>
>
>
>
Thank's a lot
regards
Achim
|
|
|