Hello Martin,

Monday, January 31, 2005, 2:50:39 AM, you wrote:

MS> Hi,
MS> since lately rulesdujour has stopped updating the rules; instead
MS> it complains that spamassassin --lint fails (which prints a lot
MS> of warnings). I've tried using sa30-check but it doesn't help.

Judging from
warning: description for SARE_RECV_IP_080032 is over 50 chars
and others, where I know that problem existed while SA 3.0.0 was in
beta, but fixed before the first production distribution, I'd guess
that you have some old custom files which are not being updated by
RDJ.

RDJ tries to pull in updates for the custom files you've told it to
manage, but the old files it doesn't replace cause these --lint
errors, and then RDJ backs out everything, not able to know that its
files are OK, and the problems are with other files.

Looking at your custom file list from the debug,

MS> debug: config: read file /etc/mail/spamassassin/70_sare_header.cf
MS> debug: config: read file /etc/mail/spamassassin/70_sare_header0.cf
MS> debug: config: read file /etc/mail/spamassassin/70_sare_header1.cf
MS> debug: config: read file /etc/mail/spamassassin/70_sare_header2.cf

70_sare_header.cf contains header0, header1, header2, and header3. So
you've duplicated entries here, by itself no big problem. But if
header is under RDJ and headerN isn't, or v.v., that could cause yor
problem.

MS> debug: config: read file /etc/mail/spamassassin/70_sare_spoof.cf
MS> /etc/mail/spamassassin/99_sare_fraud_post25x.cf

Fred -- can you confirm -- isn't 70_sare_spoof.cf a replacement for
99_sare_fraud_pos25x.cf?  If 99_ isn't being maintained because it's
obsolete, that could be contributing to this problem.

MS> debug: config: read file /etc/mail/spamassassin/antidrug.cf
Obsoleted by SpamAssassin 3.0

MS> warning: description exists for non-existent rule SPF_HELO_PASS
Isn't this part of 3.0 standard? Is there a problem with your
installation?

MS> warning: description for DATE_IN_FUTURE_48_96 is over 50 chars
Another distribrule, I think. I suspect you're pulling in some pre-3.0
distrib rules into your 3.0 installation.

MS> warning: description for SUBJ_2_NUM_PARENS is over 50 chars
That's an awfully new rule. I don't think it ever existed with more
than 50 chars in its description. Is it possible that one or more of
your files is in the wrong format (has the wrong line ending control),
so that lines are wrapping and description lines are flowing over to
the next line?

Bob Menschel



Reply via email to