Thanks Bowie, I ran it, and it seemed to update, though it gave me no info as it did, + it did restart the service. But this has still not fixed my problem. I really don't think we will be on the right track until someone tell me to start posting some of my configuration file. I would have dun it already except I don't know witch ones would help.
Thanks again. nonlin PS. I was able to find the instructions for the as-update, so for those of you who are as new to Spamassassion as I am, hear is what I found. http://wiki.apache.org/spamassassin/RuleUpdates#Using_sa-update ----- Original Message ----- From: "Bowie Bailey" <bowie_bai...@buc.com> To: <users@spamassassin.apache.org> Sent: Thursday, August 12, 2010 9:16 AM Subject: Re: Fw: Spamassassion for each site > On 8/11/2010 10:32 PM, nonlin wrote: > > Well I am not out of the Dog House yet. > > > > So, by some miracle I was able to get yum to work and was able to use it to > > update Spamassassion. I was so happy because this was the safest way to do > > this. But yum didn't have ver 3.3 available so I was able to update to: > > SpamAssassin version 3.2.4 > > running on Perl version 5.8.5 > > and I rebooted the server. > > > > So, from my understanding that should get me out of the Y2K issue. > > But, guess what. I still have the same problem, so the upgrade didn't work. > > > > Any other suggestions? > > You need to run sa-update to get the latest rules. Updating the package > only gives you the rules that were in effect when that version of SA was > released. Recent versions of SA have removed the rules from the package > altogether and require you to run sa-update after installation. > > -- > Bowie
