addressbook amiga apache apachecon apple asm australia backup bash bcel berlin blog books c cocoa cocoaheads cocoon commons conferences continuations css debian debug dependencies drools eclipse email firefox flickr funny gadgets geo git gmail google gps html http iphone ipod java javaflow jci jdeb job joost linux mail maven melbourne minijar music network objectivec osx photography plugins reviews ruby safari software spam ssl surfing svn thunderbird travel ubuntu windows wordpress
Related posts:
I just came across the Anti Spam Smtp Proxy. It seems to be a competitor to spamassassin - but it has a very different philosophy. Spamassassin only tags the mails while assp seems to block them at the SMTP level. Since there might be some false positives with statistical spam detection I would probably prefer spamassassin …but I am still fan of the idea to only accept signed emails at the SMTP level. Which goes into the assp direction…
I have used ASSP for quite a while now in its “Test Mode”, which only “Prepends” the word “Spam: ” to the subject line. This helps our users quickly identify spam, but it still allows us to avoid the negative affects of false positives in business.
You can also simply assign to individual users or domains how they want SPAM handled - either tagged or stopped - no need to keep it in test mode.