Michael wrote: > I don't think you can have SQL based per-recipient settings in a policy > bank. you either use SQL based settings OR a policy bank.
Actually you can. The associative array %sql_clause is a member of policy banks, so you can tweak SQL clauses based on which policy bank is loaded. Mind that this has nothing to do with the original question from Manthra, which only needs SQL lookups, not policy banks (which are just a distraction in that posting). > usually you use sql settings for the default INCOMING (no policy), and a > policy bank for 'clients' or 'mynets'. Policy banks affects message as a whole, and as such can not be per-recipient (as a mail message can have more than one recipient). So it only makes sense to base policy bank loading on common attributes of a message, like TCP port number, IP address of a SMTP client, a sender address, valid DKIM signatures in the message etc. Per-recipient settings are a different breed, they use a lookups mechanism: the *_maps settings, including their implied SQL and LDAP lookups. It is an unfortunate historical incident causing confusion that one of the SQL tables is named 'policy' - it has nothing to do with policy banks. Mark ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
