Hi Matt,
I resolved the issue. Thanks for pointing me in a different direction- the
rubber has not been meeting the road for about a week on this issue!
After upgrading using CPAN I am getting BAYES scores (among others from the
/usr/share/spamassassin dir). So apparently it was an installation issue.
Dec 23 18:45:12 unixserv0 MailScanner[24894]: Message jBO2iqfX025133 from
68.76.136.35 ([EMAIL PROTECTED]) to tomsawyer.com is spam,
SBL+XBL, spamcop.net, SpamAssassin (score=36.46, required 4, autolearn=spam,
BAYES_50 0.00, FORGED_RCVD_HELO 0.14, PYZOR_CHECK 3.70, RATWARE_NAME_ID
4.10, RCVD_IN_BL_SPAMCOP_NET 1.56, RCVD_IN_DSBL 2.60, RCVD_IN_NJABL_DUL
1.95, RCVD_IN_XBL 3.90, SAVE_THOUSANDS 0.40, SUBJECT_EXCESS_BASE64 0.45,
TO_CC_NONE 0.13, URIBL_AB_SURBL 3.81, URIBL_JP_SURBL 4.09, URIBL_OB_SURBL
3.01, URIBL_SC_SURBL 4.50, URIBL_WS_SURBL 2.14)
This leads me to a question about installation since in the INSTALL file it
says:
[unzip/untar the archive]
cd Mail-SpamAssassin-*
perl Makefile.PL
[option: add -DSPAMC_SSL to $CFLAGS to build an SSL-enabled spamc]
make
make install
This is how I normally done it over the past few years- install to a prefix
in /usr/local and then create a symbolic link to /usr/local/spamassassin so
that I can keep the previous version around in the event I need to recover
from a bad upgrade. I don't recall ever having the difficulty that I had
this time around.
perl Makefile.PL --PREFIX=/usr/local/spamassassin-n.nn
make
make install
ln -sf /usr/local/spamassassin-n.nn /usr/local/spamassassin
The problem is that the installer did not put the perl modules in the site
directory (/usr/perl5/site_perl/../... The spamassassin.pm module in the
site dir now (after running CPAN) shows the updated version:
#/usr/perl5# grep 3.00 /usr/perl5/site_perl/5.8.0/Mail/SpamAssassin.pm
$VERSION = "3.001000"; # update after release (same format as perl $])
The SpamAssassin.pm file from my original make, make install is here, but
obviously was not being used:
# ls -lsa /usr/local/spamassassin/lib/perl5/site_perl/5.8.0/Mail
total 53
1 drwxr-xr-x 3 root 512 Dec 12 16:08 ./
1 drwxr-xr-x 4 root 512 Dec 12 16:08 ../
1 drwxr-xr-x 10 root 1024 Dec 12 16:08 SpamAssassin/
50 -r--r--r-- 1 root 50780 Sep 13 19:07 SpamAssassin.pm
This is also version 3.001.000
In the install directions, it does not say anything about building
spamassassin and then moving perl modules manually. Am I missing something?
John
-----Original Message-----
From: Matt Kettler [mailto:[EMAIL PROTECTED]
Sent: Friday, December 23, 2005 3:08 PM
To: John Urness
Cc: users@spamassassin.apache.org
Subject: Re: Bayes Scores Skipped/Not Applied
John Urness wrote:
>
> ####/etc/mail/spamassassin/local.cf
> score ALL_TRUSTED 0 0 0 0
That is very concerning. Why'd you do that? 99.9% of the time the proper fix
is to declare a trusted_networks. Disabling this rule merely covers up one
symptom of a very pervasive problem (errant trust).
>
> use_bayes 1
> use_bayes_rules 1
> use_auto_whitelist 1
> bayes_auto_learn 1
> bayes_auto_expire 1
> bayes_expiry_max_db_size 200000
> bayes_file_mode 0777
> auto_whitelist_path
/extra/system/spamassassin/autoDB/auto-whitelist
> auto_whitelist_file_mode 0666
> bayes_path /extra/system/spamassassin/autoDB/bayes
> bayes_ignore_header X-MailScanner
> bayes_ignore_header X-MailScanner-SpamCheck bayes_ignore_header
> X-MailScanner-SpamScore bayes_ignore_header X-MailScanner-Information
Wait, why the mailscanner ignores? Are you using mailscanner? If so, stop
running spamd. MailScanner uses the perl API, so you don't need spamd, it's
just wasting memory to run it.
>
>
