You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Joe Smith <cg...@cgspam.staticcling.org> on 2004/07/29 06:32:39 UTC

Rulesdujour error

*This message was transferred with a trial version of CommuniGate(tm) Pro*
I get the following error when rulesdujour runs spamassassin --lint. 
Any ideas what I've done wrong and how I can fix this? It also says 
that there is a new version of antidrug.cf but it's actually the same 
version that I'm currently using. It seems to be adding a .2 at the end 
of the rule set even though it's the same rule set I already have. 
Here's the output from rulesdujour. I'm running this with Spamassassin 
2.63 on Mac OS X.

RulesDuJour Run Summary on 24.20.xxx.xxx:

Matt Kettler's AntiDrug has changed on 24.20.xxx.xxx.
Version line: # rev 0.65 04/28/2004

***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is:  mv -f /etc/mail/spamassassin/antidrug.cf 
/etc/mail/spamassassin/RulesDuJour/antidrug.cf.2; mv -f 
/etc/mail/spamassassin/RulesDuJour/antidrug.cf.20040728-0000 
/etc/mail/spamassassin/antidrug.cf;

Lint output: Failed to parse line in SpamAssassin configuration, 
skipping: open_redirect_list_spamcop_uri   snurl.com              
*.snurl.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   snipurl.com            *.snipurl.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   tinyclick.com          *.tinyclick.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   babyurl.com            *.babyurl.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   lin.kz                 *.lin.kz
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   *.v3.net
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   shorl.com              *.shorl.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   tinyurl.com            *.tinyurl.com
Failed to parse line in SpamAssassin configuration, skipping: 
open_redirect_list_spamcop_uri   xurl.us
razor2 check skipped:  Can't locate object method "new" via package 
"Razor2::Client::Agent" at 
///Library/Perl/5.8.1/Mail/SpamAssassin/Dns.pm line 392.
Failed to compile URI SpamAssassin tests, skipping:
	(syntax error at //etc/mail/spamassassin/spamcop_uri.cf, rule 
SPAMCOP_URI_RBL, line 1, near "eval:"
syntax error at //share/spamassassin/20_uri_tests.cf, rule URI_OFFERS, 
line 175, near ";
}"
)


Re: Rulesdujour error

Posted by Chris Thielen <cm...@someone.dhs.org>.
Hello Joe,

On Wed, 2004-07-28 at 21:32 -0700, Joe Smith wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> I get the following error when rulesdujour runs spamassassin --lint. 
> Any ideas what I've done wrong and how I can fix this? It also says 

Try running spamassassin --lint from outside of RDJ.  Do the lint errors
persist?  If so there's a configuration error.  

The open_redirect_list_spamcop_uri directive is for SURBL.  Have you
installed the SURBL stuff correctly?

> that there is a new version of antidrug.cf but it's actually the same 
> version that I'm currently using. It seems to be adding a .2 at the end 
> of the rule set even though it's the same rule set I already have. 

The .2 nomenclature is just an internal of the script while it's moving
stuff around in the temp directory.  You can safely ignore that.  Notice
that when it's in /etc/mail/spamassassin it is called antidrug.cf, not
antidrug.cf.2.

> Here's the output from rulesdujour. I'm running this with Spamassassin 
> 2.63 on Mac OS X.
> 
> RulesDuJour Run Summary on 24.20.xxx.xxx:
> 
> Matt Kettler's AntiDrug has changed on 24.20.xxx.xxx.
> Version line: # rev 0.65 04/28/2004
> 
> ***WARNING***: spamassassin --lint failed.
> Rolling configuration files back, not restarting SpamAssassin.
> Rollback command is:  mv -f /etc/mail/spamassassin/antidrug.cf 
> /etc/mail/spamassassin/RulesDuJour/antidrug.cf.2; mv -f 
> /etc/mail/spamassassin/RulesDuJour/antidrug.cf.20040728-0000 
> /etc/mail/spamassassin/antidrug.cf;
> 
> Lint output: Failed to parse line in SpamAssassin configuration, 
> skipping: open_redirect_list_spamcop_uri   snurl.com              
> *.snurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   snipurl.com            *.snipurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   tinyclick.com          *.tinyclick.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   babyurl.com            *.babyurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   lin.kz                 *.lin.kz
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   *.v3.net
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   shorl.com              *.shorl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   tinyurl.com            *.tinyurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   xurl.us

Make sure the SURBL stuff is installed properly.

> razor2 check skipped:  Can't locate object method "new" via package 
> "Razor2::Client::Agent" at 

Also make sure Razor2 is installed properly.

> ///Library/Perl/5.8.1/Mail/SpamAssassin/Dns.pm line 392.
> Failed to compile URI SpamAssassin tests, skipping:
> 	(syntax error at //etc/mail/spamassassin/spamcop_uri.cf, rule 
> SPAMCOP_URI_RBL, line 1, near "eval:"
> syntax error at //share/spamassassin/20_uri_tests.cf, rule URI_OFFERS, 
> line 175, near ";
> }"
> )
> 

-- 
Chris Thielen

Easily generate SpamAssassin rules to catch obfuscated spam phrases
(0BFU$C/\TED SPA/\/\ P|-|RA$ES): http://www.sandgnat.com/cmos/

Keep up to date with the latest third party SpamAssassin Rulesets:
http://www.exit0.us/index.php/RulesDuJour

Re: Rulesdujour error

Posted by Jeff Chan <je...@surbl.org>.
On Wednesday, July 28, 2004, 9:32:39 PM, Joe Smith wrote:
> Lint output: Failed to parse line in SpamAssassin configuration,
> skipping: open_redirect_list_spamcop_uri   snurl.com              
> *.snurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   snipurl.com            *.snipurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   tinyclick.com          *.tinyclick.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   babyurl.com            *.babyurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   lin.kz                 *.lin.kz
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   *.v3.net
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   shorl.com              *.shorl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   tinyurl.com            *.tinyurl.com
> Failed to parse line in SpamAssassin configuration, skipping: 
> open_redirect_list_spamcop_uri   xurl.us

This is ok.  It's the SpamCopURI install saying that the redirect
tests are disabled by default.  You can ignore these warnings.

Or if you use SpamCopURI version 0.19 instead, you won't get these
warnings.

> Failed to compile URI SpamAssassin tests, skipping:
>         (syntax error at //etc/mail/spamassassin/spamcop_uri.cf, rule 
> SPAMCOP_URI_RBL, line 1, near "eval:"
> syntax error at //share/spamassassin/20_uri_tests.cf, rule URI_OFFERS, 
> line 175, near ";
> }"
> )

Here is how Henry solved this:

> The problem was that even though the install copied all the files over to
> "/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/" and the command "perl 
> -MMail::SpamAssassin::PerMsgStatus -e 'print 
> $INC{"Mail/SpamAssassin/PerMsgStatus.pm"},"\n"'" returned 
> "/usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/PerMsgStatus.pm", my 
> copy of SA 2.63 was actually using the pm files in 
> "/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/" instead.
> 
> Once I copied over the pm files to the 5.8.1 directory instead, linting 
> SA 2.63 was successful and I was getting the markups I expected.

HTH,

Jeff C.
-- 
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/