On Thu, August 7, 2008 12:27, Noel Jones wrote: > Jon wrote: >> On Thu, August 7, 2008 02:39, Magnus Bäck wrote: >>> On Thu, August 7, 2008 10:01 am, Jon said: >>> >>>> On Wed, August 6, 2008 15:23, Nicolas Letellier wrote: >>>> >>>>> I'm looking for a solution to desactivate antispam solution for a >>>> few >>>>> recipients. >>> [...] >>> >>>> Yes, use the smtpd_restriction_classes... >>>> >>>> http://www.postfix.org/RESTRICTION_CLASS_README.html >>> No. Per-recipient content filtering requires multiple Postfix >>> instances. >>> >>> -- >>> Magnus Bäck >>> [EMAIL PROTECTED] >>> >> >> Why? Use the restriction classes to define which FILTER to use via >> a >> pcre or regexp script. One restriction class calls one script, >> while >> the other class calls another. Each class calls a different content >> filter. Create two different content filters, one pipes to >> spamassassin, while the other does not. >> >> -- >> Regards, >> Jon >> >> > > The FILTER result is a per-message attribute, not a > per-recipient attribute, so using restriction classes will > give unpredictable results with multi-recipient messages. > > Since unpredictable results are generally considered bad, > Magnus is correct - you need multiple instances of postfix to > do per-recipient filtering. > The reason you need multiple instances is because you need to > use transport_maps to route each recipient to the correct > filter, and transport_maps is (for all practical purposes) a > global setting. > > An alternative is to use a smarter content_filter or milter > that allows per-recipient settings. > > -- > Noel Jones >
I.C. Thanks for the explanation. -- Regards, Jon
