Re: [AMaViS-user] skip amavis for relay_domains

On 9/7/07, list-amavis-user@tgice.com <list-amavis-user@tgice.com> wrote:
> Hi guys,
>
> I just setup a Postfix + Amavis server a while back (after finally
> getting away from a Qmail installation I really didn't like).
>
> I'm using virtual domains, and a few other fancy features (like database
> storage of those virtual domain mailboxes), and for the most part I like
> the install.
>
> One small issue that's been bugging me is this:
>
> I relay email for one other domain (I'm that one's backup MX and vice
> versa), but it appears that my amavis install is scanning every email
> that comes in for them before forwarding it to their domain.
>
> That step is completely unnecessary (and possibly harmful due to
> whitelists, etc.) since that domain does it's own filtering. There are
> also of course the issues of somewhat reduced performance on my side.
>
> All that I want Postfix and/or Amavis to do is immediately forward email
> for this backup MX domain to that domain.
>
> If searched around through several documents with very little success.
> I have already implemented an approach to stop scanning of locally
> generated email (defined by SASL authenticated users). Would doing the
> same thing for relay_domains be done similarly?
>
> I'm sure I've missed something fairly simple as I'm sure anyone who
> relays email as a backup MX would want the same behavior.
>
> transport_maps wouldn't have anything to do with this, would it?
>

There are a couple ways to do this.
This is one where you configure amavisd-new to bypass recipients:
http://www200.pair.com/mecham/spam/bypassing.html#9

If you have another IP address available:
http://www200.pair.com/mecham/spam/bypassing.html#3

You may be tempted to use a check_recipient_access map to work around
amavisd-new (by setting a transport override that reinjects the
message back to the reinjection port):

smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/amavis_bypass
<...>

/etc/postfix/amavis_bypass:
domain.tld FILTER smtp:[127.0.0.1]:10025

But:
"It may be worth mentioning that in Postfix, content_filter and FILTER
are mechanisms used to override a given message's transport. All
recipients of the message are affected. It is not acceptable to use
the FILTER mechanism in a check_recipient_access map to attempt to
override the transport for a particular recipient when there is a
possibility a message for that recipient may also be addressed to
other recipients. The result would be all of those recipients are
filtered, whether they are listed in the map or not."

--
Gary V

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/