Configuration file not being read?

[Rob Starr]

Thanks Julian,

I've set those 4 setting to blank but "MailScanner --debug --debug-sa" still
shows "/usr/share/spamassassin" for default rules dir.  My understanding is
that this line should say "/var/lib/spamassassin/3.002003", right?

Also, ls -lu shows my MailScanner.conf file is indeed being accessed.

When I set this:
SpamAssassin Default Rules Dir = /var/lib/spamassassin/3.002003

I get these errors:
debug: Failed to parse line in SpamAssassin configuration, skipping: include
updates_spamassassin_org/10_default_prefs.cf
debug: Failed to parse line in SpamAssassin configuration, skipping: include
updates_spamassassin_org/20_advance_fee.cf
...


Rob Starr    B.Eng

-----Original Message-----
From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Julian
Field
Sent: October-30-07 10:57 AM
To: MailScanner discussion
Subject: Re: Configuration file not being read?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Rob Starr wrote:
> Hi there,
>
> I'm using MailScanner 4.64.3 + Postfix + SpamAssassin 3.2.3.
>
> I believe this is a MailScanner configuration problem.  My issue is
> that spamassassin rules from sa-update are not being used (and I've
> verified they exist in /var/lib/spamassassin/3.002003).
>
> A MailScanner lint test reports no issues.  A SpamAssassin lint
> test also reports no issues, and shows the sa-update rules being
> used.  Spamassassin -t /tmp/spam.sample shows the rules being used.
>
>
> "MailScanner --debug --debug-sa": ---------------------------------
>  In Debugging mode, not forking... SpamAssassin temp dir =
> /var/spool/MailScanner/incoming/SpamAssassin-Temp debug: Score set
> 0 chosen. debug: running in taint mode? no debug: ignore: test
> message to precompile patterns and load modules debug: using
> "/usr/share/spamassassin" for default rules dir debug: using
> "/etc/mail/spamassassin" for site rules dir debug: using
> "/var/spool/postfix/.spamassassin/user_prefs" for user prefs file
> ...
>
> /etc/MailScanner/MailScanner.conf snippet:
> ----------------------------------------- SpamAssassin Site Rules
> Dir = /etc/mail/spamassassin SpamAssassin Local Rules Dir =
> SpamAssassin Local State Dir = /var/lib/spamassassin SpamAssassin
> Default Rules Dir =
Set all those 4 settings to blank. It should pick up the right places
automatically anyway.

Also, remember that the "last accessed" datestamp on a file can be
used to tell you if a config file is being used. A "ls -lu" will show
the last-accessed instead of last-modified stamps on each file, so you
can see if it is updated (and hence the file was read) by any
particular command.

Jules

- --
Julian Field MEng CITP
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ0Y6EfZZRxQVtlQRArKpAKD7mdw6IEUQxnFV+l4CT0bPSGBJiQCgmwIm
XY9y+OMPSl+epiPYYySMV5U=
=Sni7
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk

-- 
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!