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.20060517-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.
> Would it help if I shortened those names?
You could, or you could wait until SARE fixes the rules.
> Am I really the only one who is having this problem?
I haven't noticed it yet.
