Karsten Bräckelmann-2 wrote:
> 
> I guess the subject is incorrect. You are indeed running 3.2.3. ;)
> 
> Upgraded, you just said. In previous posts you said "installed". That
> makes a difference.
> 
> How did you install 3.3? Given the Perl module dependency issues you
> mentioned, I guess via CPAN. Did you uninstall 3.2? Nope...
> 
> 

Hmmm....thanks for your reply Karsten.

I already had v3.2.3 running on the system, so I thought was upgrading! I
followed the instructions on the "Upgrading to the latest version" page
(http://wiki.apache.org/spamassassin/UpgradingVersion) which suggested
installing by CPAN to upgrade so that's what I did (I didn't think I was
being foolish!!).

No I didn't uninstall 3.2.3 - I didn't know I was supposed to.


Karsten Bräckelmann-2 wrote:
> 
> 
> Restarted spamd *how*? Using the same old init script?
> 
> 

Yes, executed /etc/init.d/spamd restart (again I didn't think I was being
foolish!)


Karsten Bräckelmann-2 wrote:
> 
> 
> The init script most likely calls spamd, where it has been installed
> previously. The new 3.3 install probably uses a different prefix, and
> thus is not used by the init script.
> 
> Also keep in mind, your $PATH likely uses a different order to find
> something like sa-update or sa-learn, than Perl uses to pick up its
> M::SA module.
> 
> 

You're getting beyond the limit of my knowledge here. Is there an idiots
guide that you could point me to inorder to try and work through your
suggestions?


Karsten Bräckelmann-2 wrote:
> 
> 
> What does 'spamd --version' report? What about 'which spamd'? What about
> finding all spamd executable scripts on your system?
> 
> 

If I just issue a spamd --version at the bash prompt, it does report back as
SpamAssassin Server version 3.3.1 and as to which spamd, I seem to have 3:
/user/bin/spamd  /user/sbin/spamd and also /use/bin/X11/spamd

However, I guess I'm now confused as to why spamc is calling the old spamd
(v3.2.3) when if I issue spamd from a bash prompt it uses the new one
(v3.3.1).


Karsten Bräckelmann-2 wrote:
> 
> 
>> So why am I getting 3.2.3 still in the header of newly received mails?
> 
> Because... it is actually running. :)
> 
> 

New I avoid upgrading for a reason. Can you offer any suggestion as to what
I should do next to sort the mess I've created out?

Thanks, David

-- 
View this message in context: 
http://old.nabble.com/X-Spam-Version-Checker-reports-3.2.3-but-running-3.3.1---Why--tp29351374p29351627.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Reply via email to