Spamassassin mostly stoped working after clamav/spamassasin update installation

[Kevin Miller]

Julian Field wrote:
> The KAM ruleset, how do you fetch it? If you do it without using
> sa-update, and just wget it or similar, then you want to put it into
> /etc/mail/spamassassin.

The KAM ruleset does live in /etc/mail/spamassassin.  It's updated by
/etc/cron.daily/KAM.cf.sh per your post from a year or so ago and is
working fine.  Sorry if that was confusing.

It was the spamassassin rules that were missing.  I poked I prodded
around quite a bit, and finally just ran sa-update on it's own.  That
complained about an invalid or missing gpg key, but had a couple lines
on how to import the key for spamassassin.  Don't know how it got
borked.  I imported the keys and then reran sa-update.  After I did
that, the latest spamassassin files came over OK.  I suspect that may
have been the problem all along, but since I was initially running
/etc/cron.daily/update_spamassassin I never saw the output (even w/the
-D option in /etc/sysconfig/MailScanner).

I noticed in my poking & prodding that I update_spamassassin was enabled
in /etc/cron.daily and I also was running sa-update in roots crontab.
It's been so long I can't recall why that was, but in looking through
the archive I noted in the release notes of a 4.6X release of
MailScanner that it fixed the call to sa-update.  So I guess I can
remove the sa-update crontab entry, and update_spamassassin will take
care of both the SARE rules as well as the spamassassin rules, yes?
(SARE rules channel is defined in /etc/sysconfig/MailScanner, btw.)

Thanks...

...Kevin
-- 
Kevin Miller                Registered Linux User No: 307357
CBJ MIS Dept.               Network Systems Admin., Mail Admin.
155 South Seward Street     ph: (907) 586-0242
Juneau, Alaska 99801        fax: (907 586-4500