Please, don't CC me. I subscribe to the list. Fred wrote: > We use action_bounce to stop mail from coming in for 5,000+ accounts > and all of our customers love it. You will always have 1 person who > doesn't want their mail scanned no matter what. It is doable in an > ISP environment but it takes some effort to get things working > smoothly.
Being able to configure just about everything on a per-user basis helps. On the system I have MD calling SA, that's not a practical option due to general system load (oldish hardware hosting ~25 domains- web/ftp/mail/etc). On another system, SA is called at delivery, and that system is about three layers deep in our mail system anyway. :/ The only thing I'm comfortable deleting outright are virus mail and spam that can be identified based solely on the sender's email address- not very many of those any more! > Be familiar with > creating nice rules, set your blocking threshold high like 6.5+ 6.5 on systems here would result in ~20% more FNs, and no appreciable reduction in FPs (I haven't heard of one in several months). It took a bit of tweaking at first, but except for a few specific customers, I haven't changed from the default threshold at 5. I've also been fairly aggressive about telling customers to report messages that were handled incorrectly; feedback from the people getting the mail (or not, as the case may be) is the best way to find out what's working. I've *also* had a couple of cases where a filter customer called to complain about the increase in spam to "a few a week". So I check on how many messages are getting tagged on their account... 50-100/day. That made them think a bit. <g> -kgd -- Get your mouse off of there! You don't know where that email has been!
