On Wed, 16 Jun 2004, Bowie Bailey wrote:
> SpamAssassin works quite well with courier. You can either use it by
> itself during delivery with maildrop or use it as a courierfilter via
> amavisd-new.
I agree.
I would make the following additions, however:
I do something like this (actually, I deliver to a spam folder, but you
get the idea):
exception {
xfilter "/usr/bin/spamassassin --local"
}
if ( /^X-Spam-Status: Yes,/:h || /^X-Spam-Flag: Yes,/:h )
{
log "Dropping SPAM"
EXITCODE=0
exit
}
Points to note:
1. wrap the call to spamassassin (or spamc or whatever) in exception,
otherwise mail won't get delivered at all if there is a problem.
2. use :h on the match to constrict yourself to headers
3. reminder: matches are by default case insensitive (yay!)
4. I enabled bayesian learning and auto learning or whatever. After
the initial training (about a day), I get < 10 SPAMS a *day* that slip
through. I haven't futzed with or otherwise had to interact with it,
other than using 'sa-learn --spam' to tell spam assassin that it
misclassified a spam (the < 10 a day I get). I use a local alias so I
can just forward it to the right address and my .mailfilter will take
care of it.
--
Ensign Walnut approaches Dr. Crusher with caution...
Jon Nelson <[EMAIL PROTECTED]>
C and Python Code Gardener
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
