I guess the subject is incorrect. You are indeed running 3.2.3. ;)
On Wed, 2010-08-04 at 14:18 -0700, Happy Chap wrote:
> I've just upgraded from SpamAssassin 3.2.3 to 3.3.1 and it all appeared to
> install correctly. However, X-Spam-Version-Checker is still coming up as
> 3.2.3 after restarting spamd. Can anyone suggest what I've done wrong?
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...
> If I try:
>
> perl -MMail::SpamAssassin -e 'print $Mail::SpamAssassin::VERSION."\n";'
>
> it reports 3.003001, so I think I genuinely am running version 3.3.1 and I
> have killed all spamd & restarted them.
Restarted spamd *how*? Using the same old init script?
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.
What does 'spamd --version' report? What about 'which spamd'? What about
finding all spamd executable scripts on your system?
> So why am I getting 3.2.3 still in the header of newly received mails?
Because... it is actually running. :)
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
