Can Someone Help With SpamBayes Problem?

Home » CentOS » Can Someone Help With SpamBayes Problem?
CentOS 7 Comments

I’ve posted to the SpamBayes users list, but there seems to be no traffic there, so I’ve had no replies. If there is anyone here using SpamBayes, I’d appreciate some advice or at least suggestions…. I’m running CentOS 5.8 here.

Day before yesterday I decided to look and see if there was a newer SpamBayes than I was then using. lo and behold, there was. I was using 1.1a4, and there was a 1.1a6. so I downloaded and installed it. bad move.

Having done that, I now have no spam filtering at all. I run my own sendmail mail server here, and it uses procmail to deliver. Procmail invokes one of the SpamBayes tools for every email, and it adds a X-SpamBayes header with its determination of spamminess. except that now it doesn’t.

the nightly retrain event (a cron job) also fails, with complaints about invalid syntax in:

File “/usr/lib/python2.4/site-packages/lockfile-0.9.1-py2.4.egg/lockfile/linklockfile.py”, line 6
from . import (LockBase, LockFailed, NotLocked, NotMyLock, LockTimeout,
^
SyntaxError: invalid syntax

a little snooping around at python.org shows that the “from . import” syntax was added in python 2.5. However, on CentOS 5.8 we still have Python 2.4.3. (never mind that the docs on SpamBayes claim it will run on Python 2.2, they’re plainly wrong).

So, I tried to reinstall SpamBayes 1.1a4 over top of what I had. It appeared to install (to the extent that the info displayed when the installer runs means anything), but it doesn’t work either. no spam filtering, no nightly cron job.

I’m guessing I’ll have to figure out, in detail, which files were installed by the 1.1a6 installation and go remove each individual one then try reinstalling 1.1a4.

Unless someone can suggest a better path to try. I’d appreciate any suggestions any of you may wish to make.

thanks in advance!

Fred

7 thoughts on - Can Someone Help With SpamBayes Problem?

  • it’s a tar.gz. you unzip it and run “python setup.py install” which is, I gather, the normal way to install Python stuff (except, of course, for those things in a RPM or DEB or whatever package). As far as I can figure out by staring blankly at the code in setup.py, there isn’t any (obvious)
    uninstall function.

  • fred smith wrote:

    All I can suggest then is tar -tvfz file.tar.gz > filelist, then feed that to find and exec rm {} \;

    mark

  • yeah, I’m working on that. but it doesn’t appear to be quite that simple. :(

    The setup.py proggie appears to do a bunch futzing around with creating/modifying files before squirreling them away in various places.

    I’ve grabbed from the screen a log of the things it says its doing, from which I hope to be able to derive the list of things to purge.

    Fred

  • Mark, et al:

    OK, that works. the installation generates a long list of actions, but in the end there are only about 20 files installed, which simplifies things, once one reads thru all the actions leading up to their installation.

    having done that, I then re-un-tar.gz’d the archive for the oldest version (the one I was originally running) and reinstalled it and it is now working.

    (I re-extracted it, because the installation process does its various machinations in subdirs of the extraction’s target directory and at least some of it gets left in place afterwards, so I wanted to make sure it was a clean install.)

    whatta pain this was!

    thanks for the sympathy and ideas!

    Fred

  • Hmm… I didn’t realize that EPEL offered spambayes. I’ll keep that in mind for the next time I rebuild that system.

    per my later emails, I did resolve the problem, so it’s not urgent anymore.

    thanks for the suggestion, though.

    Fred

LEAVE A COMMENT