SARE rules question

[Matt Kettler]

Diane Rolland wrote:
> I have tried to install/configure SARE Rules and RulesDeJour from 
> http://www.rulesemporium.com/rules.htm and when I run the below command 
> I get the following failures.
>  
> /usr/bin/spamassassin -p /etc/MailScanner/spam.assassin.prefs.conf --lint
>  
> Failed to parse line in SpamAssassin configuration, skipping: 
> lock_method flock
> Failed to parse line in SpamAssassin configuration, skipping: 
> use_auto_whitelist 0
> Failed to parse line in SpamAssassin configuration, skipping: 
> envelope_sender_header X-MailScanner-From
>  
> By commenting them out of the spam.assassin.prefs.conf file for the 
> above items I get the --lint to run without error, but I'm not sure what 
> that means to my configuration.
>  
> I have SA 2.55, MailScanner-4.50.15-1 (I know, out of date)

not just out of date.. ancient. SA 2.55 is from may of 2003.

2.55 is also subject to a remotely exploitable DoS attack by sending it a 
malformed email.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0796

Before messing with SARE and RDJ, I'd seriously look at upgrading.

In any event your version is way too old to support those options.

The flock is really just a performance tweak, you won't miss it. This allows SA 
to use a faster lock method for your bayes database, at the expense of not being 
NFS compatible.

The envelope_sender_header, well, there's no equivalent functionality in your 
version, but this allows SA to look at nonstandard headers when trying to detect 
the envelope sender. This really would only affect your whitelist_from* and 
blacklist_from* efforts.

use_auto_whitelist allows you to disable the AWL, but in your version, it 
defaults to off anyway unless you pass a command-line parameter. (in 2.60 they 
changed it to default-on and added a config option. In 3.1.0 it became a plugin, 
so nowdays you can just disable it by not loading it.)