Re: SA 3.0 and Greylisting (new version)

On Sat, Nov 27, 2004 at 11:25:10PM -0600, Marc F. Clemente wrote:
> I assume that the patch is Greylisting.pm in the CVS...  How does it work?
 
Damn, people are actually watching CVS :)
I haven't checked in the docs yet.
 
> I compiled and installed the CVS version of sa-exim.
> 
> I copied Greylisting.pm to /usr/share/perl5/Mail/SpamAssassin/Plugin
> 
> I added "loadplugin Mail::Spamassassin::Plugin::Greylisting" to 
> /etc/spamassassin/init.pre
> 
> Now what do I do?  What are the important config options in 
> sa-exim.conf?  Do I still need "header GREYLIST_ISWHITE ..." in 
> /etc/spamassassin/local.cf?  What configuration changes do I need to 
> make, as I upgrade from spamassassin 2.x to 3.x?

This is what I use:

# Be careful to put numbers between double quotes, or they won't be passed on
loadplugin Greylisting /usr/share/perl5/Mail/SpamAssassin/Plugin/Greylisting.pm
header GREYLIST_ISWHITE eval:greylisting("( 'dir' => '/var/spool/sa-exim/tuplets'; 'method' => 'dir'; 'greylistsecs' => '1800'; 'dontgreylistthreshold' => 11; 'connectiphdr' => 'X-SA-Exim-Connect-IP'; 'envfromhdr' => 'X-SA-Exim-Mail-From'; 'rcpttohdr' => 'X-SA-Exim-Rcpt-To'; 'greylistnullfrom' => 1; 'greylistfourthbyte' => 0 )")
describe GREYLIST_ISWHITE The incoming server has been whitelisted for this receipient and sender
score GREYLIST_ISWHITE  -1.5
# Run SpamAssassin last, after all other rules.
# (lets us not greylist a host that is sending spam, otherwise this rule might
# set a sufficiently negative score that the next spam would be allowed in)
priority GREYLIST_ISWHITE 99999

There is still a -T dependency buglet that I'm working on, which is why I
haven't announced it yet :)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/   |   Finger [email protected] for PGP key