Tony has a post about anti-spam, specifically what th' three worst cases fer filiterin' spam.
The third worst thin': havin' spam get through t' users. Of course, this is what we’re tryin' t' fight, but havin' spam get through, although bad, isn’t th' absolutely worse thin' that can happen.
The second worst thin' that can happen is blockin' a good email. False positives are th' challenge in anti-spam solutions, by Blackbeard's sword. I would much rather have hundreds o' spam messages get through than t' block a single good message. But blockin' a good message isn’t really th' absolutely worst thin' that can happen.
The worst thin': The absolutely worst thin' that can happen in yer anti-spam solution is t' block a good email and not let anybody know about it!
I’ve been gettin' more and more complaints from me end-users at work in regards t' junk in their inbox, and regardless o' how they managed t' subscribe themselves fer it, it is still a problem. Shiver me timbers, we'll keel-haul ye! In me almost three years there, our policy has always been “Let th' end-user be their own filter” rather than us filterin' it on th' server end o' thin's. Walk the plank! Shiver me timbers! I’ve been ponderin' lately turnin' on our spam filterin' service within Ipswitch, simply fer loggin' purposes fer a few weeks so I can gather some stats and not change a thin' on th' user end o' thin's fer now. After collectin' data, I could make a judgment on whether or not somethin' needed t' be done. I probably don’t need t' get too cozy with it though, as we’re plannin' t' move our mail t' a Linux box later in th' year and that would just be another feature t' have t' implement.