Matt Kettler wrote:
Michael Scheidell wrote:
3.18 is unsupported.
please update to latest versions.
Well, it's as supported or unsupported as any other version of
SpamAssassin is. No version of SpamAssassin is "supported" by the SA
team beyond the advice given on this list. (sure, some third parties
offer supported services, but that's another ball of wax and not
relevant here.)

However, more to the point, it is getting a bit old. sa-update can only
do so much, and at some point, you need updated code to keep abreast of
the current trends in spam. If accuracy is your problem, updating to a
current release should be your first step. Beyond that, look for common
mistakes like ALL_TRUSTED firing off on spam (a sure sign of a broken
trust path, see http://wiki.apache.org/spamassassin/TrustPath)

As for the error messages, it looks like for some reason your stock
ruleset is getting parsed twice. You didn't happen to copy some or all
of the stock ruleset into /etc/mail/spamassassin by mistake, did you?

Thanks, guys the problem is that for SuSE 10.0 3.1.8 is the max, and the
last time I update a 10.0 to the lastest everything broke. And the major
thing for me that perl is still at 5.8.7, don't you have to be 5.8.8 or
higher for the lastest stuff.

I am looking into the stuff you recommend, and no I haven't updated
another into /etc/mail/spamassassing, but I have found out that
sa-update places the lastest greatest updates in /var/lib/spamassasin
and suse by default places the test files into /usr/share/spamassassin I
think that is the problem. So know I have to figure out how to kill one
of them with out screwing up things.

Again thanks.

Payne

Reply via email to