Dear friends, I don't mean to be condescending but it look like no one is really reading my posts.
I had run sa-update, /var/lib/spamassassin/3.002004 owner is root and I ran sa-update as root. and it looked like it updated. and I just ran it again now as per these latest instructions, rebooted the server to be therow and things are the same. Now as to the path we are on, someone had insisted that it was a Y2K bug that was causing the problem. But that dos not make any since to me. because Spamassassion is WORKING and properly, but just not for all email accounts. Doesn't Spamassassion have a feature for disabling it for an individual user? What happens if one of my clients tell me to turn it off for there account only. You should be able to do that, Right? Well I would guess that would be the most likely cause for my problem, a feather being miss used, Why are we not looking it that first? I just don't know were to go to check that. Are you all shore its a technical problem, not a configuration problem? nonlin PS, I have never worked with Spamassassion before and I found the manuals for it not clear enough to help. The things that I find most helpful are examples. like seeing a peace of a confirmation file and having just what needs to set pointing out, There is nothing better then that for helping me to understated. ----- Original Message ----- From: "Bowie Bailey" <bowie_bai...@buc.com> To: <users@spamassassin.apache.org> Sent: Thursday, August 12, 2010 5:29 PM Subject: Re: Fw: Spamassassion for each site > On 8/12/2010 4:40 PM, nonlin wrote: > > 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. > > > > Running sa-update for the stock rules is very easy. Just go to a prompt > as a user who has permission to write to /var/lib/spamassassin/3.002004 > and run 'sa-update'. It will grab any updated rules. Then just restart > spamd to enable the new rules. By default, sa-update gives no output > unless there is a problem. > > The man page gives details on various options, but you should not have > to set any of them unless you are trying to update third-party rules. > > If you ran sa-update and are still getting the problem with the date > rule, there must be another problem. Anyone know if the date issue was > fixed on SA 3.2.4? > > At worst, you can do the quick fix. Find the name of the rule causing > the problem (I don't remember and am too lazy to look), and add a score > line to your local.cf like this: > > score RULE_NAME 0 > > This will disable the rule. > > You really need to stay up to date with the versions if you want the > best performance. Only the current version gets regular rule updates. > Older versions are only updated to fix major problems (such as the date > issue you are having). > > -- > Bowie
