CertaintyTech - Ed Henderson wrote: > I have been testing the auto_whitelist (AWL) feature sitewide in a single > database and have come to realize that it does have a downside - namely that > if false negatives get thru then eventually their address is added to the > AWL and then SA will never catch them as Spam. Any way around this? I am > using v2.01 stable. > > --- > Ed. [...]
I was think about this exact same thing today, as I put SA into production for my 400+ users (800+ email accounts - and without a hiccup, I might add ;^). I wanted to have the default be to not filter because that's what people are used to, so I set the default theshold to 100 and gave user instructions for using the web-based management script to set themselves up for a threshold of 5. Then it hits me! I'm going to be accepting mail form every Tom, Dick, and Spamford on the net, and they are ALL going to get added to the site-wide whitelist. My initial solution: I wiped out the whitelist and shut off that feature. My next solution will be to make a "awl_threshold" option that I can set to something reasonable (like 3) that will allow me to use AWL sitewide even when somepeople set thier threshold to 100 or 999 for that matter. Can anyone see any problem with this approach? Don -- -------------------------------------------------------- Donald L. Greer, Jr [EMAIL PROTECTED] System Administrator Voice: 512-300-0176 AustinTX http://www.AustinTX.COM/ All opinions are my own. Flame me directly. "I don't necessarily believe software should be free... but if you pay for it, it should work!" -- Me _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
