That looks a little expensive -- you'll collect a rather long
whitelist over time. I'm attaching the scripts I'm using nowadays;
this is based on a Berkeley DB I put in my $HOME. As a secondary
use, I'm also using this whitelist for mutt's query feature.
Mutt configuration settings:
set query_command="~/whitelist/wl_query.pl %s"
set sendmail="/home/roessler/Devel/whitelist/sendmail-wrapper-db.pl -oem -oi"
.procmailrc:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
:0Whc
| $HOME/whitelist/check_db.pl
:0Wef
| formail -I "X-No-Spam: whitelist"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
You can then guard your spamassassin invocation with something like
this:
:0
* !^X-No-Spam: whitelist
{
...
}
(I'm running the whitelist scripts on my laptop, and spamassassin
on a server, so what I actually use is based on occasionally
updating spamassassin's whitelist.)
--
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.
On 2003-10-14 18:09:52 -0400, Alexy Khrabrov wrote:
> From: Alexy Khrabrov <braver@xxxxxxxxx>
> To: Alexy Khrabrov <braver@xxxxxxxxx>
> Cc: Mutt Users <mutt-users@xxxxxxxx>
> Date: Tue, 14 Oct 2003 18:09:52 -0400
> Subject: Re: A simple whitelisting script
> X-Spam-Level:
>
>
> And, of course, the corresponding procmail recipe is:
>
> ########## WHITELIST
>
> :0 fhw:
> * ? formail -x"From:" -x"From" -x"Sender:" | grep -is -f $HOME/.whitelist
> | formail -A "X-Mark: whitelist"
>
> :0 A
> $ORGMAIL
> ##########
>
> I mark various spam-fighting stages with special headers,
> then color them in mutt.
>
> --
> Cheers,
> Alexy Khrabrov :: www.setup.org :: Age Quod Agis
>
Attachment:
check_db.pl
Description: Perl program
Attachment:
sendmail-wrapper-db.pl
Description: Perl program
Attachment:
wl_query.pl
Description: Perl program