James E. Pratt schreef:
-----Original Message-----
From: Jo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 17, 2006 9:05 AM
To: Matt Kettler
Cc: users@spamassassin.apache.org
Subject: Re: problem with using SARE rules, names longer than 22 chars
Matt Kettler wrote:
Jo wrote:
Hi,
We're using spamassassin-3.0.5-3.el4 with amavisd-new-2.4.1-1.el4.rf.
Since yesterday I'm receiving this message when downloading the SARE
rules:
***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is: mv -f
/etc/mail/spamassassin/72_sare_redirect_post3.0.0.cf
/etc/mail/spamassassin/RulesDuJour/72_sare_redirect_post3.0.0.cf.2;
mv
-f
/etc/mail/spamassassin/RulesDuJour/72_sare_redirect_post3.0.0.cf.2006051
7-0758
/etc/mail/spamassassin/72_sare_redirect_post3.0.0.cf; mv -f
/etc/mail/spamassassin/70_sare_header0.cf
/etc/mail/spamassassin/RulesDuJour/70_sare_header0.cf.2; mv -f
/etc/mail/spamassassin/RulesDuJour/70_sare_header0.cf.20060517-0758
/etc/mail/spamassassin/70_sare_header0.cf;
Lint output: warning: rule 'SARE_MULT_SEXCLUBGMAILA' is over 22 chars
warning: rule 'SARE_BOUNDARY_0264192082' is over 22 chars
warning: rule 'SARE_MSGID_HEX30XIDSRVR' is over 22 chars
warning: rule 'SARE_BOUNDARY_D118112147' is over 22 chars
warning: rule 'SARE_HEAD_MIME_INVALID32' is over 22 chars
warning: rule 'SARE_MULT_SUBJR_XBNCETR' is over 22 chars
warning: rule 'SARE_FROM_SPAM_NAME2A177' is over 22 chars
lint: 7 issues detected. please rerun with debug enabled for more
information.
Are these simply problems with the names?
Yes, but it's not really a problem.
Thanks for your answer. I only saw after I sent the mail that they were
only warnings and not errors. I'm a bit less worried now. I thought I
had a version mismatch or something like that.
Would it help if I shortened those names?
You could, or you could wait until SARE fixes the rules.
Still it seems to strange to arbitrarily limit the length of those names
to 22 characters.
Am I really the only one who is having this problem?
I haven't noticed it yet.
I had the same probllem with sa 3.000004
Anyhow, i solved it by changing the trusted ruleset entry
"SARE_HEADER_0" to "SARE_HEADER_X31" as advised on rulesemporium.com,
and all works fine now.
regards,
Jamie
That seems to have solved the problem, even when it's X30 instead of X31.
Thanks,
Jo
