Hello Farid,
Sunday, March 6, 2005, 10:27:45 AM, you wrote:
FI> This is the debug output produces by the shell :
FI> ***WARNING***: spamassassin -D --lint failed.
I'm not familiar with RDJ -- is the -D parameter there part of the
usual script, or something you added? I was under the impression that
RDJ checked for any --lint output, and rolled back if it found any. -D
*will* generate output, and it might be causing RDJ to see problems
when there really aren't any.
FI> Rolling configuration files back, not restarting SpamAssassin.
FI> Rollback command is: mv -f /etc/mail/spamassassin/tripwire.cf
FI> /etc/mail/spamassassin/RulesDuJour/99_FVGT_Tripwire.cf.2; rm -f
FI> /etc/mail/spamassassin/tripwire.cf; mv -f
FI> /etc/mail/spamassassin/evilnumbers.cf
FI> /etc/mail/spamassassin/RulesDuJour/evilnumbers.cf.2; rm -f
FI> /etc/mail/spamassassin/evilnumbers.cf; mv -f
FI> /etc/mail/spamassassin/70_sare_random.cf
FI> /etc/mail/spamassassin/RulesDuJour/70_sare_random.cf.2; rm -f
FI> /etc/mail/spamassassin/70_sare_random.cf;
The SARE files rolled back were tripwire, evilnumbers, and random. The
header config files aren't mentioned. I did an update to the header
files yesterday, and warning messages below reference some of those
rules. What is the status of the header files as far as your
configuration and your RDJ go?
FI> Lint output: debug: SpamAssassin version 3.0.2
FI> ...
FI> config: SpamAssassin failed to parse line, skipping: rewrite_subject
1
FI> config: SpamAssassin failed to parse line, skipping: subject_tag
*SPAM*
FI> [...etc...]
You have --lint errors here that are probably in your local.cf
Even though these errors have nothing to do with the files managed by
RDJ, they will cause RDJ failures.
FI> warning: score set for non-existent rule SARE_HEAD_XBEEN
FI> warning: score set for non-existent rule SARE_FREE_WEBM_MYWAY
FI> [...etc...]
These are the header rules I mentioned earlier. I don't see the header
files mentioned anywhere. If you have scores set for these rules in
your local.cf, but are not including those files, that will also cause
your problem.
FI> Can someone explain to me how to solve all the config issues
FI> detected ? (config: SpamAssassin failed to parse line)
Have you checked the config docs?
Bob Menschel
