Client side spam killing - what’s good?
Posted on February 7, 2006
2 Comments
I still use Outlook 2k3 at home. Frankly, I’ve yet to find anything that I like better, which is maybe a bit embarassing? Or maybe is just a comfort factor — plus a decade’s worth of archives. Regardless, it is my email client of choice.
I have been using SpamBayes’ plugin for outlook for most of the last year. I’m very impressed and now use it on all my various home and work machines. It trains very well and I have to say it really doesn’t ever mis-classify for me, which is a huge plus. All that praise aside, know what it doesn’t do? It doesn’t automatically kill (delete) detected spam. In other words, spam will always go to the spam folder for, presumably, final review. A nice safety net I suppose…
Heck, I trust it enough now that I’d really rather it just killed detected spam automatically. But I can’t seem to find that as an option. Thus, I’m wondering: should I look for another tool?
If you run any sort of “client side” (as opposed to server filtering) processes, I’d be interested to hear what you use and if it works well. For the moment, I’m wondering if I can write some outlook rules to just wack anything that shows up in the “junk mail” folder. I guess that’d be simplest?
Tags: outlook, spam, spamBayes
Possibly Related Posts
Comments
2 Responses to “Client side spam killing - what’s good?”
Leave a Reply



Can you compound SpamBayes’ “move spam to folder” behavior with an Outlook rule that says “when new messages arrive in spam folder, move them to trash”?
Alas, I tried. Outlook doesn’t seem to want to trigger a rule based on an email showing up in a specific folder.
Found something at the faq as well.