Jo Rhett wrote: > Mark Martinec wrote: >>>> Are you using SQL? If so, a catchall user with spam_lover "N" would >>>> have precedence over this static hash. >>> Yes, I am using SQL but I don't think for this map. But that's why I >>> tried to include the existing map, in case something was set in sql. >> SQL field has priority over statical *_maps. So either let SQL >> return correct Y or N for required recipients, or let that >> field in SQL be NULL, so that lookups will fall back to statical maps. > > It doesn't appear that sql is enable for this, only for policy and > black/white listing.
To be more specific, we're using the default white/blacklist settings, which don't appear to have any place to store spam_lovers information. Here's the documentation of that. # The SQL select clause to check sender in per-recipient whitelist/blacklist # The first SELECT argument '?' will be users.id from recipient SQL lookup, # the %k will be sender addresses (e.g. full address, domain only, catchall). # The default value is: # $sql_select_white_black_list = 'SELECT wb FROM wblist,mailaddr'. # ' WHERE (wblist.rid=?) AND (wblist.sid=mailaddr.id)'. # ' AND (mailaddr.email IN (%k))'. # ' ORDER BY mailaddr.priority DESC'; # -- Jo Rhett Net Consonance ... net philanthropy, open source and other randomness ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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/
