On Sat, 16 Jun 2007 17:02:29 -0500
Lindsay Haisley <[EMAIL PROTECTED]> wrote:

> On Sat, 2007-06-16 at 17:53 -0400, Michael B Allen wrote:
> > When I run ./rules_du_jour I just get a mess of errors about trying
> > to write to /etc/spamassassin which does not exist.
> 
> Make /etc/spamassassin a symlink to /etc/mail/spamassassin.  This is how
> Gentoo Linux has it set up.

Hi Lindsay,

Actually from reading the script I was able to create a suitable config.

> >  Apparently CentOS
> > uses /etc/mail/spamassassin/ and more so /usr/share/spamassassin/ for
> > cf files. Is there any documentation for this script?
> 
> /var/lib/spamassassin/rules_du_jour has copious comments with usage
> instructions and commented settable options in the script itself.  Take
> a look at it with your favorite text editor.

Yup.

But now I see the TRIPWIRE config is croaking on some HTML in the cf:

***WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.
Rollback command is:  mv -f /etc/mail/spamassassin/tripwire.cf 
/etc/mail/spamassassin/RulesDuJour/99_FVGT_Tripwire.cf.2; rm -f 
/etc/mail/spamassassin/tripwire.cf; mv -f 
/etc/mail/spamassassin/70_sare_evilnum0.cf 
/etc/mail/spamassassin/RulesDuJour/70_sare_evilnum0.cf.2; rm -f 
/etc/mail/spamassassin/70_sare_evilnum0.cf; mv -f 
/etc/mail/spamassassin/70_sare_random.cf 
/etc/mail/spamassassin/RulesDuJour/70_sare_random.cf.2; rm -f 
/etc/mail/spamassassin/70_sare_random.cf;

Lint output: [7529] warn: config: failed to parse line, skipping: 
<HTML><HEAD><META HTTP-EQUIV="Refresh" CONTENT="0.1">
[7529] warn: config: failed to parse line, skipping: <META HTTP-EQUIV="Pragma" 
CONTENT="no-cache">
[7529] warn: config: failed to parse line, skipping: <META HTTP-EQUIV="Expires" 
CONTENT="-1">
[7529] warn: config: failed to parse line, skipping: </HEAD></HTML>
[7529] warn: lint: 4 issues detected, please rerun with debug enabled for more 
information

Removing it from TRUSTED_RULESETS resolved the problem but apparently
something is not optimal.

Mike

Reply via email to