On 8/12/2010 7:37 PM, nonlin wrote: > 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.
Sorry if I came across that I wasn't paying attention to your posts. I generally just respond to each message as it comes through, so I sometimes don't remember the history of the problem if it is not mentioned in the current post. Your previous post mentioned looking for instructions for sa-update, so I was just pointing out that 90% of the time, no instructions are necessary, you just run the command and let it do its thing. You mentioned the Y2K (FH_DATE_PAST_20XX) problem in a previous post, so I assumed you had already determined that this was your problem and my comments were relevant to this. My comment about staying up to date still holds. SA 3.2.4 is over 2.5 years old now. The newer versions have bug fixes and updated rules. Anti-spam software is like antivirus software -- if you want it to catch everything, you have to stay up to date. I'm aware that you updated via yum and 3.2.4 was the latest available. In that case, I would start looking for a different repo. I don't see a mention of which distro you are running, but the rpmforge repo for CentOS and RedHat has 3.3.1. As for your problem, you should post an example on one of the pastebin sites so we can see exactly what is happening. If your problems are intermittent or only for some users, it may also be useful to describe how you have integrated SA. For example, my server calls spamc from maildrop and then maildrop filters the mail based on the headers added. My home system talks to spamd directly via a filter, rejects high scoring spam, and then sends the rest for delivery and sorting via maildrop. The most useful manual I have found for SA is the man page for Mail::SpamAssassin::Conf. Other than that, if you ask a specific question on this list, most people will be happy to either answer directly or at least point you to the proper documentation. -- Bowie
