Benedict. > I have created a mysql database based on cutting and pasting bits out of > README.sql.txt which creates 4 tables, mailaddr, policy, users and wblist.
Ok. > Am I right in thinking that if I set a policy up in the policy table, then > set up a user in the users table, then I can modify the behaviour of > amavisd new on a per user basis by having a policy for each user? Yes. > Or on a per domain basis by having a policy per domain? Yes. If multiple users (or domains) would have the same settings, there is no need to give them individual copies of policy entries, but you certainly may. > Can I also assume that because a user is listed in users that amavisd-new > treats them as local Yes. If you want otherwise, you may add a field 'local' (values Y or N) and you may have this setting explicit. There is usually no need for it though, the default suffices. > and will clean mail for them? Spam checking (and other checks) are performed regardless of whether recipient is considered local or not. > Will it mark spam for them if it is outbound? X-Spam* header fields are only inserted for local recipients (inbound and all-internal mail). X-Virus-Scanned header fields are always inserted (as long as virus scanning was done), regardless of recipient being local or not. Again: spam checks are performed regardless or recipient being local, so quarantining, bounces etc applies to outbound mail as well, unless configured otherwise (bypass_*). > (Or do i control that with ip based relaying?) Client's IP address can be use to switch policy banks (not to be confused with SQL table 'policy' - an unfortunate similarity in names). It gives you a choice to treat mail from 'mynetworks' (or other criteria) differently, e.g. to be less restrictive on banned names and perhaps allow higher spam score or turn off some checks entirely. > Can I also ask what amavisd new will do with the contents of mailaddr and > wblist? wblist establishes a relationship between sender address (mailaddr) and recipient address (table users). A recipient (individual or domain) can treat a sender (individual or domain) as blacklisted or as whitelisted, or (better choice) give it few score points (positive or negative), which is called 'soft-black(white)listing'. Mark ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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/
