Stuart, > I recently upgraded to amavisd-new 2.3.3 and SQL based configuration. I > have several different local domains but all users are treated the same. > I only want to have one policy and one white/black list for all users. > I am having trouble getting this to work with the SQL configuration.
> In particular, I had to create separate entries in the users table for > each domain in order to mark them as local. Right. If you want to rely on automatic value of users.local field, you need a separate entry for each local domain (see README.lookups). A non-existent field 'local' (in 'users' and 'policy' tables) implies true except for a catchall entry (@.). You can however add an explicit field policy.local or users.local and keep it at NULL. This will avoid the automatism and let lookups for 'local' fall back to static lookup tables, so you may list your local domains in @local_domains_maps if this is what you prefer. Having done so, you are then free to have only one 'policy' entry to which all users.policy_id refer to. Mark > Now the wblist table > requires rid to match against the users table which would mean that I > would have to create redundant wblist entries for each domain? ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ 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/
