>-----Original Message-----
>From: Yanick Quirion [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 14, 2004 10:41 AM
>To: [EMAIL PROTECTED]
>Subject: Spamassassin 3.0.0 pre2 --lint problem
>
>
>Hi all,
>
>Yesterday I updated my version of spamassassin to version 
>3.0.0 pre2. It
>works fine except I got a lots of errors into default rules when I ran
>command "spamassassin -lint"
>
>Here is an output of those errors:
>
>[venus]:/root# spamassassin --lint
*snip*
>warning: score set for non-existent rule URIBL_PH_SURBL
>warning: score set for non-existent rule URIBL_SC_SURBL
>warning: score set for non-existent rule SARE_RD_SAFE_GT
>warning: score set for non-existent rule SARE_RD_SAFE_TINY
>warning: score set for non-existent rule URIBL_WS_SURBL
>warning: score set for non-existent rule SARE_RD_SAFE_MKSHRT
>warning: score set for non-existent rule URIBL_SBL
>lint: 70 issues detected.  please rerun with debug enabled for more
>information.
>
>[venus]:/root# spamassassin -V
>SpamAssassin version 3.0.0-pre2
>  running on Perl version 5.8.3
>
>I'm using some rules from "http://www.rulesemporium.com/"; and 
>I also use
>RulesDujour to update them. When RDJ script got errors from 
>spamassassin
>--lint command line, it will rollback all updated rules. With version
>2.63 I don't have this problem and I'm using exactly the same rules.
>
>If you look at the few last warning, URIBL... comes with spamassassin
>itself and it detects error. I also tried to remove all 
>downloaded rules
>and keep only SA rules and URIBL are still in warning.
>
>Does anybody know how to resolve this problem?
>

Well we just haven't got around to fixing the name lengths. But these work
fine. When 3.0 is officially released, we will retire rule sets that have
been incorporated into 3.0

The URIBL errors are just what they say. Your install can't find the actuall
rules, only scores. It isn't setup correctly. 

--Chris

Reply via email to