Unless something has changed with the most recent versions of SpamAssassin
I see two configuraton errors present.
1) YOu do NOT use /use/share/spamassassin to store rules. They belong
in /etc/mail/spamassassin or some other such place.
2) Why are you running tripwire.cf (obsolete) and 99_FGTTripWire.cf at
the same time?
(Note that I do NOT use RulesDuJour here. I have my own script for
handling updates. It's a ridiculously simple bash script that I can
read. {^_-} So maybe using /usr/share/spamassassin is some form of
silly RDJ action. That is a directory that is utterly wiped out with
each upgrade of SpamAssassin, though. So anything in it gets lost.)
{^_^}
----- Original Message -----
From: "Nigel Frankcom" <[EMAIL PROTECTED]>
On Thu, 21 Jun 2007 03:07:52 -0400, Phil Barnett <[EMAIL PROTECTED]>
wrote:
Is anyone else getting these failed messages on their tripwire.cf updates?
I've been getting this message for several days now.
It looks to me like the new tripwire.cf is very broken.
---------- Forwarded Message ----------
Subject: RulesDuJour Run Summary on taz5.fiberhosting.net
Date: Thursday 21 June 2007 02:26
From:
To:
RulesDuJour Run Summary on taz5.fiberhosting.net:
TripWire has changed on taz5.fiberhosting.net.
Version line:
***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is: mv -f /usr/share/spamassassin/tripwire.cf
/usr/share/spamassassin/RulesDuJour/99_
-------------------------------------------------------
FVGT_Tripwire.cf.2; mv -f
/usr/share/spamassassin/RulesDuJour/tripwire.cf.20070621-0225
/usr/share/spamassassin/tripwire.cf;
Lint output: [24363] warn: config: failed to parse line, skipping:
<HTML><HEAD><META HTTP-EQUIV="Refresh" CONTENT="0.1"> [24363] warn:
config:
failed to parse line, skipping: <META HTTP-EQUIV="Pragma"
CONTENT="no-cache"> [24363] warn: config: failed to parse line, skipping:
<META HTTP-EQUIV="Expires" CONTENT="-1"> [24363] warn: config: failed to
parse line, skipping: </HEAD></HTML> [24363] warn: lint: 4 issues
detected,
please rerun with debug enabled for more information
I've been getting the same for weeks. I ended up manually updating
rules; especially the stock one since more and more seem to be
slipping through.
The problems seemed to start after the DDoS on rulesemporium; since
then I've not been able to get any sense out of it via RDJ.
When I manually update it all lint's clean. Time consuming but it
works
Hope that helps
Nigel
