Hi All,

thanks for the comments ...

I think that Noel's idea is cool, although we have the overhead for an
e-mail that might not be checked, but in the end, it should work all the
time with less complexity in Postfix.

Thanks Again

Charles


On Mon, 2008-06-09 at 23:54 -0500, Noel Jones wrote:
> Clifton Royston wrote:
> > On Sat, Jun 07, 2008 at 11:21:54AM +0200, lartc wrote:
> >> hi all,
> >>
> >> i've got a postfix/amavis/cyrus setup that is working.
> >>
> >> certain domains that i handle should not be processed by amavis -- is
> >> there a directive available in postfix to tell it not to send to a
> >> content filter based on the recipient domain, but to go ahead and
> >> process normally (forward, etc, etc)
> > 
> >   The (RHS) right-hand-side of any access map in Postfix can contain a
> > number of different directives, one of which can be FILTER with an
> > IP/port specifier, saying which content-filter you want it to go to. 
> > 
> >   Two ways to do this are:
> > 
> > 1) to have no default content-filter set in main.cf or master.cf, and
> > to use a recipient access map on the domains to turn the filter on for
> > the domains you want to send through amavisd;
> > 
> > 2) to have your default send it through amavisd, and to use the access
> > map to make the domains which you want to bypass amavisd send their
> > content-filter directly to the Postfix instance which amavisd usually
> > reinjects into *after* its processing.
> > 
> >   If you've already got a working set-up, you should find it pretty
> > easy and quick to add this via either of these methods.
> >   -- Clifton
> > 
> 
> Note that using FILTER in a check_recipient_access table is 
> not robust because there can only be one FILTER action per 
> message and different recipients in a multi-recipient message 
> may require different FILTER settings.  Designs that work 
> right "most of the time" should be avoided.
> 
> It should be sufficient to add domains/recipients you don't 
> want filtered to amavisd-new's bypass_*_checks_maps and 
> *_lovers_maps.  The mail will still pass through amavisd-new, 
> but won't actually be checked for anything.  This simplifies 
> mail flow and keeps configuration information in one place.
> 
> If the mail must not pass through amavisd-new at all, then use 
> postfix transport_maps entries to direct the mail.  As 
> transport_maps is a global setting, this requires multiple 
> postfix instances rather than master.cf gymnastics.
> 
> 

-- 
"simplified chinese" is not nearly as easy as they would
have you believe ... a superlative oxymoron" --anonymous


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to