Spam Check

[tgaugh]

I am getting the error below on many messages:

/spamassassin/20_uri_tests.cf" requires version 2.44 of SpamAssassin, but this is code version 2.5...

Can I edit all the .cf (assuming I re-edit after DSM updates involving SA) to the correct version of SA? OR is this an informational message and it is still performing the filter?

Also, is there a way or .cf to just shoot all update messages to /dev/null versus updating and still forwarding all the spam?

thx

[gonecrazy]

you can just update to the lattest stable spam assassin package I belive its 2.63 (the 3.0 package should be out soon) as far as i can tell dsm dosn't require anything special about the spam assassin package and it will work "out of the box".

[tgaugh]

Got it, but without upgrading do you know if this is an informational error, or is there really something wrong?

It is appending this message but is it working?

[gonecrazy]

yea i think its still working but skipping that rule set, which is going to decrease your effectiveness at catching spam.

what might have happened is that you started out with 2.44 but, a system update (up2date or yum) updated the package to a newer 2.5x version, and had a issue replace the rule, you might just try a update with your system updater on that package.

eg:

yum update spamassassin or up2date spamassassin

[gonecrazy]

i ment had a issue replaceing that rule



*ponders why he can't edit his own posts*

[tgaugh]

Gathering header information file(s) from server(s)
Server: Red Hat Linux 9 - i386 - Base
Server: Red Hat Linux 9 - Updates
Finding updated packages
Downloading needed headers
spamassassin is installed and the latest version.
No actions to take

[gonecrazy]

do a rpm -q spamassassin

What version do you have installed?

This is what mine says:

rpm -q spamassassin
spamassassin-2.63-0.2

[tgaugh]

spamassassin-2.44-11.8.x

[gonecrazy]

You must be using up2date, as they are not activly updating packages any more.

I would sugest updating to the newest version, you can do this 2 ways, either grabing yum and installing it to update your system now that up2date is no more. (http://www.fedoralegacy.org/) or grab the current rpm by

wget http://old.spamassassin.org/released/RPMs/perl-Mail-SpamAssassin-2.63-1.i386.rpm

wget http://old.spamassassin.org/released/RPMs/spamassassin-2.63-1.i386.rpm

wget http://old.spamassassin.org/released/RPMs/spamassassin-tools-2.63-1.i386.rpm

then install them

rpm -U perl-Mail-SpamAssassin-2.63-1.i386.rpm
rpm -U spamassassin-*

you might have to use --force in there and maby --nodeps so that it upgrades without complaining about the old version or just uninstall the old version and then install the new version.

After you have the new version installed you should be able to see the new version number in the header information of e-mails that pass through the system

[tgaugh]

No, that response was from yum not up2date.

Let me try pulling the latest package and forcing it on. Thanks for you help thus far though.