Matt wrote: > Thanks...
> My boss wants to lower all of our user's thresholds to 1.0 automatically > (they currently default to 3.0), because about FIVE users have called and > complained of 10 false positives per day. > I keep telling him that without full statistical filtering, you can't be > 100% accurate, and the amount of false positives is going to be ridiculous > with a setting of 1.0 > But then again, he's the businessman who runs the company, so all I can do > is provide him with info..... I gotta get a real job soon where boss's > actually understand TECHNICAL talk and find alternate methods (such as > creating custom filtering rules) instead of lowering thresholds. > -Matt As has been shown recently, spam that has been slipping under the wire recently has been carefully crafted to resemble legitimate mail. It's simply difficult to weed that stuff out. Lowering the threshold to that low of a level is not cool. If your users have access to their spam, that only means they will have to spend more time looking through it to find legitimate mail, so there is no gain in productivity. If they choose to discard (or ignore) at that level (I can't believe someone would actually do that), then they can only blame themselves when important mail disappears (maybe when some mail the boss sends gets trashed he will understand). Didn't you get my email?, No. I personally find it better to keep the threshold high, tolerate what comes in, and forget about what goes in the spam bin. I think it's more efficient. If I get repetitive spam, I act on it with a custom rule or content filter, or IP address reject, whatever I think might be effective. Custom tweaks usually catch stuff for about a week. I have not tried it, but I always thought this was interesting and would be curious if anyone else is using: http://sourceforge.net/projects/rblpolicyd/ Gary V ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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/
