I think the only real solution to this problem (which is one I was aware of -- it crops up quickly even with per-user whitelists) is to change the way the auto-whitelisting works, to do the average score/regression to the mean system I talked about a few days ago. It's an enhancement I'm planning to add sometime soon, but first I'm trying to work on squashing some more critical bugs in the 2.0x release. For now, people might consider turning off auto-whitelisting (particularly site-wide) if they don't want the false-negative rate to go up.
C on 1/31/02 9:39 PM, CertaintyTech - Ed Henderson at [EMAIL PROTECTED] wrote: >> >> 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 >> > > How does solve my original problem of false negatives? all that it would > take would be a few marginally spammy messages < 5 then once the threshhold > is reached then they can Spam away! _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
