Integrating SpamAssassin and BestPractical's RT

%expand% Integrating SpamAssassin and BestPractical's RT %set(body,%html-clean({

The filter "Filters::SpamAssassin.pm" that is included with RT doesn't function for a number of reasons, not the least of which is that SpamAssassin doesn't know what a Mime::Entity is (it uses it's own mail format).

At first I wrote 2 versions of the plugin, but then i combined them, seeing as the included one doesn't work at all.

http://www.documentroot.com/SpamAssassin.pm

It uses the "spamd" daemon ... to speed things up which is faster, unless you have Mail::Spamassassin preloaded under mod_perl (assuming you do things that way). If you do have it running that way, you can forget spamd (but isn't it nice you can run your spam checker on another box if you load gets high...).

Of course many people seem to just use fetchmail on some box somewhere, and then rely on that box's builtin mail filtering (can anyone say gmail) for spam. Which works well, but I like the idea of "owning" my mail filter.

Nor all I have to do is add a "spam" status, and some scrips to auto-train spamassasin's bayesian filter on them ... fun.

}))


Bracing against the wind
www.documentroot.com

View Archive

Free Blog Commenter & Counter

Memebot: Free Website Hosting

Americans for Approval Voting

2002 WTC Pics: Aug 12 Aug 16 Aug 30 Sep 11 Sep 23 Oct 24

Shop with Bitcoin At Amazon

Yvette's Weblog

All sites by me

RSS for this site

Lo! In the east against the blazing shadow of a rising sun, there come four men striding in unison, each step a journey, against the terrible winds.

Thursday, August 07, 2008

Integrating SpamAssassin and BestPractical's RT
Posted 1:42 AM

The filter "Filters::SpamAssassin.pm" that is included with RT doesn't function for a number of reasons, not the least of which is that SpamAssassin doesn't know what a Mime::Entity is (it uses it's own mail format).

At first I wrote 2 versions of the plugin, but then i combined them, seeing as the included one doesn't work at all.

http://www.documentroot.com/SpamAssassin.pm

It uses the "spamd" daemon ... to speed things up which is faster, unless you have Mail::Spamassassin preloaded under mod_perl (assuming you do things that way). If you do have it running that way, you can forget spamd (but isn't it nice you can run your spam checker on another box if you load gets high...).

Of course many people seem to just use fetchmail on some box somewhere, and then rely on that box's builtin mail filtering (can anyone say gmail) for spam. Which works well, but I like the idea of "owning" my mail filter.

Nor all I have to do is add a "spam" status, and some scrips to auto-train spamassasin's bayesian filter on them ... fun.

[View/Post Comments] [Digg] [Del.icio.us] [Stumble]

| Bloghop: | Blogarama | Technorati | Blogwise