-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Coyner <[EMAIL PROTECTED]> wrote:
> I recently installed Spamassassin and have been successfully using
> it with Mutt and Procmail.  So far it's doing a great job of
> catching spam, but the ocassional one does get through. 

Same here! Couldn't do without daemonized spamd and spamc connecting
to it via Procmail. 

> When one does get through, I've been submitting it by hitting S in
> the index, which pipes it to spamassassin -d.

Why _on earth_ do you want to run SA with -d switch in this kind of
situation? 

   -d, --remove-markup                Remove spam reports from a message

What it is exactly you want SpamAssassin to do to the mail when you
press 'S'?

> Any idea why I might be getting the mailcap entry message?
> Improperly config'd mailcap?  Maybe, but why would it be looking for
> audio/x-wav files?

This isn't a solution to your question, but I felt like showing how
I'm handling spam that gets through my filters. Here we go:

I press 'S' on a spam, which adds the From-header to this file formail
goes through everytime mail comes in, and if the address can be found
from this file, the mail gets /dev/nulled. It also adds a
"blacklist_from foo@bar" entry in ~/.spamassassin/user_prefs. And then
it moves the mail to spam folder. 

Here's the macro:

   macro pager S |~/.mutt/addspam.sh<enter>s="spam\n"

And the 'addspam.sh' looks like this:

[...]

#!/bin/sh
#
# $Id: addspam.sh,v 1.5 2002/08/11 07:48:09 ekhowl Exp $

SPAMASSASSINFILE="/home/ekhowl/.spamassassin/user_prefs"
SPAMMERSFILE="/home/ekhowl/.procmail/spammers"

for x in `awk '{if ( $1 == "From:") { for (x = 1 ; x <= NF ;
x++) { if ($x ~ /[^ ]*@[^ ]*/) { gsub("<|>", "", $x) ; print $x } }
}}'`
do
echo $x >> $SPAMMERSFILE
echo "blacklist_from $x" >> $SPAMASSASSINFILE
done

[...]

I'm not taking any responsibility for the ugliness of this script. ;-)
I also apologize for making this mail this long. Anyway, this is how
I handle every spam that SA or my other feeble filters doesn't catch.
Not too much trouble and "enough automation", IMO. Works for me.

- -- 
Jussi Ekholm  --  <[EMAIL PROTECTED]>  --  http://erppimaa.ihku.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9X7Z5AtEARxQQCB4RAtGWAKC6mVBS24fW3f2VifL8BX/kvW3uSACeIR/y
roUGrhZjbz3fE/2tqGuRHm0=
=wUh5
-----END PGP SIGNATURE-----

Reply via email to