Mark Martinec wrote the following on 5/10/2007 4:27 PM -0800: > On Friday May 11 2007 00:51:14 Bill Landry wrote: > >> So explain a situation where the first filter would *not* apply. As >> written, it applies to everything and anything after >> "check_client_access pcre:/etc/postfix/filter_outbound" is useless, as >> everything will be sent to the first content_filter and thus, end of >> "smtpd_recipient_restrictions" processing. >> > > The FILTER action only replaces the current content_filter setting > and does not stop processing restrictions. Multiple FILTER > actions can all stick their value into a content_filter > one after another, whatever remains there when some restriction > finally does terminate processing (or the list runs out) > then applies as the chosen setting for the content_filter. > > Ah, ok, now the light bulb is lit. Thanks for the explanation, I didn't realize that was how the filter action worked, nor did I understand what Gary was saying. It makes sense now.
Thanks, Bill ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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/
