SA 2.63 upgrade
dickenson at CFMC.COM
Sat Feb 7 02:06:05 GMT 2004
Thanks for the pointer about old .cf files not working with a new version.
This lead me to the solution.
I will try to remember this for future updates and leave a trail for those
The install from the RPM was the cause of the problem. I now remember
dealing with this at some time in the past as well.
The perl-Mail-SpamAssassin-2.63-1 RPM file put stuff in the 5.6.1 directory
but I am running perl 5.8.0 so the new .cf files got installed but as the
new perl stuff got put into the "wrong" place I was still using the old
version of SA.
Moving a bit of stuff around fixed the problem. I also made a link from
5.6.1 to 5.8.0 so maybe I will remember this in the future.
I guess the correct thing to do would be to uninstall the RPMs and install
SA some other way. Maybe another day. One wasted day is enough this time
Again thanks much!
mailto:dickenson at cfmc.com
Computers for Marketing Corporation
> From: James Gray <james at grayonline.id.au>
> Reply-To: james at grayonline.id.au
> Date: Sat, 7 Feb 2004 09:43:04 +1100
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: SA 2.63 upgrade
> On Sat, 7 Feb 2004 07:16 am, Jim Dickenson wrote:
>> I am seeing the same problem. I updated, as I have always done, via RPM.
>> What I am seeing is that none of the standard rules are getting tripped,
>> just the RulesDuJour additions I have installed.
>> I originally had the RulesDuJour .cf file in /usr/share/spamassassin
>> along with the ones distributed with SA. I have moved them to
>> /etc/mail/spamassassin but I am still seeing the same behavior.
>> I also see that all the stuff that is spam is being auto-learned in my
>> bayes files. What is the best way to stop using bayes files and then
>> creating new ones. I need to get this problem sorted out before I can try
>> to get my bayes files loaded again.
>> Jim Dickenson
> I posted a similar problem to this list a few weeks ago when I upgraded my
> FreeBSD box via "ports" (fBSD "packages" for want of a better term). All
> my custom rules were being tripped but none of the standard SA2.63 rules.
> The problem was that between 2.61 -> 2.63 the fBSD port maintainer had
> moved the location of the standard rules from /usr/share/spamassassin to
> /usr/local/share/spamassassin. All I needed to do was manually tell
> MailScanner where the SpamAssassin files were, restart and voila!
> Here's the relevent lines from MailScanner.conf:
> SpamAssassin Local Rules Dir = /etc/mail/spamassassin
> SpamAssassin Default Rules Dir = /usr/local/share/spamassassin
> Hope that helps :) The problem is that all the default SA rules are
> version-specific. You can ONLY use 2.63 rules with SA2.63 etc. Sounds
> like your spamassassin is finding the older 2.61 rules with the 2.63 engine
> which means it will ignore them - have a look in the standard rules files;
> there's a "require 2.63" or something similar at the top of each one. DONT
> change this BTW, this will break things even worse than it already is.
> Fortune cookies says:
> The price one pays for pursuing any profession, or calling, is an intimate
> knowledge of its ugly side. -- James Baldwin
More information about the MailScanner