Peter H. Lemieux wrote:
OK, I've ransacked mailing lists for over an hour now and have yet to
find an answer to this question.
Until a couple of months ago I was running SA 2.64 under MailScanner
4.36.4, both installed from RPMs on a RedHat 7.3 system. I've been
migrating to a CentOS 4.4 box running SA 3.1.7 and MailScanner 4.56.8,
both again installed from RPMs.
I began to get suspicious about the new installation when I ran a couple
of spams through spamassassin -t. Rules like DATE_IN_PAST showed up
in those tests, but they didn't get tripped when the message was scanned
by SA under MailScanner. It looked as though MailScanner was simply
ignoring the default rules in /usr/share/spamassassin. A few scans of
maillog for some of the default rule names didn't show any hits over a
period of weeks. For instance, there are no log entries in the new
installation for commonly-hit rules like 'HTML_[0-9]+' or 'DATE_IN'.
Except... I do get hits for the URIBL rules in
/usr/share/spamassassin/20_dnsbl_tests.cf. A locate dnsbl search
doesn't turn up any other copies of these rules in the directory tree.
So I tried an experiment based on the approach described in
http://article.gmane.org/gmane.mail.virus.mailscanner/4499 of running
spamassassin -D --lint -C /etc/MailScanner/spam.assassin.rules.conf
and the output showed that only /etc/mail/spamassassin was used. I also
get a lot of non-existent rule errors that don't appear if I just run
spamassassin -D --lint. Running a normal lint without the config file
specified shows rules being read from both /etc/mail/spamassassin and
/usr/share/spamassassin.
I've looked all over the system to see if I can find some setting that
differentiates between these two situations. I've even tried it with an
empty /etc/MailScanner/spam.assassin.rules.conf. I've looked in places
like /root/.spamassassin, /var/spool/MailScanner/spamassassin, and the
like, and can't find anything that would divert SA from using
/usr/share/spamassassin when invoked by MailScanner.
I read a bunch of postings to the MailScanner list and found nothing
helpful. My next step is to run MailScanner in debugging mode, I guess,
but I'd prefer not to have to interrupt production. If any of you have
any clues about what my problem is, I'd appreciate it. If not, I off to
debugging land.
Peter
Peter
one for the MailScanner list really
but in MaiLScanner.conf what's your setting for SpamAssassin Local
State Dir, but as SA is displaying the same simptoms when run outside
of MailScanner it could be something wrong with the
spam.assassin.rules.conf settings.
BTW /etc/mail/spamassassin/mailscanner.cf should now be a symbolic to
spam.assassin.rules.conf so you shouldn't need to put in in -C when
running spamassassin from the command line anymore.
I'd ask on the IRC channel or mailscanner email list as it sounds like
your install has problems...
--
Martin Hepworth
Senior Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.
**
