> > |-----Original Message----- > |From: Keith Hackworth [mailto:[EMAIL PROTECTED] > |Sent: 02 November 2004 15:40 > |To: marti > |Cc: Spamassassin > |Subject: Re: Error after upgrading to 3.0.1 > | > |> After upgrading from 3.0.0 to the latest version I get the following > |> error:- > |> > |> ERROR! spamassassin script is v3.000000, but using modules > |v3.000001! > |> > |> Any idea what scrip its refering to, spamassassin --lint -D worked > |> just fine, but cant fire up spamd. > |> > |> Martin > |> > |> > | > |I had the same problem - copy the files from > |/opt/local/scripts to /opt/local/bin > | > |Keith > | > > I don't have such a directory, it installs to > /usr/lib/perl5/site_perl/5.8.0/Mail > /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin > /usr/bin/spamc > /usr/bin/spamd > /etc/mail/spamassassin > > Using locate I can confirm there are no other directories other than a > backup directory I put all the rules in, so can only think that it dosent > like one of the scripts that came in the Mail-SpamAssassin-3.0.1.tar.gz. > > What do you class as a script, is that a .cf? or could that be any file in > the package? Is there anyway to get a debug output from spamd so I can see > which script its borking on? > > I have run out of ideas now as to whats causing this, is there a bug in > make > install, this should just be a simple process, this is ridiculous. > > Martin > >
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
