At 4:49 PM EDT on July 29 Rob 'Feztaa' Park sent off:
> Alas! Andre Berger spake thus:
> > By the way, what would an exmaple
^^^^^^^^^^
It's not mutt, but since I don't have time to read the procmail list...
> > procmail rule to add a sender to the spamassassin blacklist look
> > like?
>
> Probably something along the lines of this (but I'm a little rusty;
> the flags are probably wrong):
>
> :0 Wh:
> * <some spam heuristic, like all caps subject lines>
*X-Spam-Flag: Yes
(unchecked) would use the result of all applied spamassassin tests.
> |grep "^From: "|<some sed to extract info from the header> >> killfile
I think I got this "addysort" tidbit from Gilbert "linuxbrit" somebody, to use
instead of sed.
#!/usr/bin/perl -wn
# Picks out the actual address from the "From:" line
unless (/\</) { print; } else { print /<([^>]+)/, "\n"; }
> :0 a:
> spamfolder
>
But what's the point? I love spamassassin because it lets me *avoid*
blacklists, and their maintenance, and filter on the spamminess of the message
itself. (unlike, say, twerp /. moderators... :-P ) I suppose you could check
the blacklist first, and skip spamassassin if it matches, to save some
computation, but my preSA experience with a personal blacklist is that there's
only a handful of spammers* that this is worthwhile for, because they don't
change their address.
*and I'm not sure they're even spammers (so I haven't razored** them) or just
mailing lists with overly open subscription policies. But they smell spammy
enough that I'm too chicken to "unsubscribe".
** An interesting alternative to blacklisting.
--
Minds that have nothing to confer find little to perceive. - Wordsworth
Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/
PGP Key: http://astro.utoronto.ca/~reid/pgp.html
msg29946/pgp00000.pgp
Description: PGP signature
