\begin{Anand Kumria}
> This means, though, that in order to be effective more spam should be
> reported to MAPS if possible. Gus pointed out
> <URL: http://spam.sourceforge.net/> and that you can interface that with
> Pine / mutt. As well you can sort/score on the basis of that header
> using things like procmail.
for mutt, using spam.pl from spam.sourceforge.net, i do this:
have a ~/.spam/from with my email address (the address generated by
the local mta isn't the one i want)
and a ~/.spam/friends listing all the domains i receive mail through -
anything else is part of the problem.
then in ~/.muttrc:
macro index S "<pipe-message>~/bin/spam.pl -e -w<enter>" "Send spam notification"
macro pager S "<pipe-message>~/bin/spam.pl -e -w<enter>" "Send spam notification"
so hitting `S' pipes the current message off to the spam.pl
script.
you want to test it fairly thoroughly first.
since i realised this list *does* preserve enough headers (sometime
earlier this week), i will be complaining about all spam i see using
this method.
> We hope to have some procmail snippets and some instructions shortly
> but for those of you who know how to do this already this might help
> cut down on the amount of spam received.
off the top of my head, completely untested:
~/.procmailrc:
:0 h
* ^X-RBL-Warning:
/dev/null
to be a little less violent, replace "/dev/null" with a file that you
might even check one day.
this one just adds a Precedence: header, but doesn't delete the
message. later procmail rules can be used to redirect it, etc:
:0 fhw
* ^X-RBL-Warning:
|formail -I"Precedence: junk"
and this one is just silly:
:0 fhw
* ^X-RBL-Warning: \/.*$
|formail -I"X-Message-Flag: spam, see: $MATCH"
see procmail(1) and procmailrc(5)
--
- Gus
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
