Another possible way to deal with this would be to put 'NG' (without quotes) into Suspicious Countries (CountryCodeRe).
Ensure that Do Suspicious Country Scoring (DoSenderBase) is set to "Score". Under "Scoring Settings", change Suspicious Country Code (sbsccValencePB) to a value higher than the (ASSP v1) default of 10, I use 20. Take a look at the messages that are making it through and see how much it will take to put them "over the edge" so to speak and block them. Set the penalty accordingly. Of course these settings are good for ASSP v1, some of them might be different in ASSP v2. Phil Quesinberry Q Systems Engineering, Inc. Electronic Controls and Embedded Systems Development http://www.qsystemsengineering.com ---------- Dale <[email protected]> schreibt: >419 scam That depends how your Bayesian is handling it. Bayesian should really really catch it. To reach then the limit for message scoring is is sufficient to put "nigeria" or similar into bombSuspiciousRe. ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
