> |-----Original Message----- > |From: Keith Hackworth [mailto:[EMAIL PROTECTED] > |Sent: 02 November 2004 16:57 > |To: marti > |Cc: Spamassassin > |Subject: RE: Error after upgrading to 3.0.1 > | > | > |When I got this error, it meant I had 2 copies of spamassassin > |executable installed on my system with one set of libraries. > | > |When I installed SA on my Solaris system running perl 5.8.4 > |from CPAN (perl -MCPAN -e shell\n CPAN> install SpamAssassin), > |it created all the scripts (spamassassin, spamd, spamc, etc) > |in a directory /opt/local/scripts instead of /opt/local/bin > |(where it had installed all previous versions). If you do a > |"which spamassassin" and "spamassassin --version", it'll more > |than likely say 3.0.0 (or some other back-rev version). I > |figured this out by looking at the install output to see > |exactly where it put the spamassassin executables and realized > |it wasn't in /opt/local/bin. I had to move the scripts to the > |/opt/local/bin directory by hand. > | > |Keith > | > > Well I tried the install via CPAM but with the exact same result > > All I can do is reiterate that I don't have 2 locations for old and new > install they are both installed in same directory, the .cf say they are > the > new version but still get ERROR! spamassassin script is v3.000000, but > using modules v3.000001! > > Surely spamassassin dosent scan the HDD for all .cf ? The only old files I > have are by backup files in another directory. > > Can anyone else suggest whats going on? > >
This has nothing to do with .cf files. It is purely a problem with running the wrong version of sa. Do this: find / --name spamassassin --print It will show all instances of spamassassin (unfortunately, it will also give you time to go to lunch) Run each of these instances with a --version argument and see what happens. Keith
