Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Interesting spam test

On Thu, Mar 31, 2005 at 01:26:13AM -0500, David Kramer wrote:
> I came up with my own technique, which works well, but has only one minor 
> (to me) problem with it.
> Postfix feeds mail to Mailman via the aliases table like so:
> mailman:             "|/usr/lib/mailman/mail/mailman post mailman"
> ....
> So first I put spamc in the pipe:
> mailman:             "|/usr/bin/spamc |/usr/lib/mailman/mail/mailman post 
> mailman"
> Now spamassassin will put in the X-Spam... headers.
> Next, newer versions of Mailman let you trap spam by looking for regular 
> expressions.  You can either look for the "X-Spam-Status: Yes" (if you want 
> to control the trip point with spamassassin), or look for the 
> "X-Spam-Level: \*\*\*\*\*" (if you want to control the trup point with 
> Mailman)
> I testted this all out, and there's only one problem.  If the message is 
> reported as spam, spamassassin will wrap the message in mime and put the 
> "Spam detection software, running on the system..." message in front of it. 
>    If you decide that it was NOT spam, then you would have to copy/paste 
> the original mail into a new mail and you lose the sender.
> Can you think of a way around this problem?

What happens if you filter through spamassassin rather than spamc?:

mailman: "|/usr/bin/spamassassin -P |/usr/lib/mailman/mail/mailman post mailman" 


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /