Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On 04.08.10 14:54, Happy Chap wrote: 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!!). OMG. Could someone push the CPAN section on that wiki page to last place, marked as DO NOT INSTALL FROM CPAN UNLESS YOUR DISTRO DOESN'T PROVIDE SPAMASSASSIN -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. A day without sunshine is like, night.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Thu, 2010-08-05 at 10:23 +0200, Matus UHLAR - fantomas wrote:
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!!).
OMG. Could someone push the CPAN section on that wiki page to last place,
Sure. You can. It's a wiki...
marked as
DO NOT INSTALL FROM CPAN UNLESS YOUR DISTRO DOESN'T PROVIDE SPAMASSASSIN
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Thu, 2010-08-05 at 10:23 +0200, Matus UHLAR - fantomas wrote: 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!!). OMG. Could someone push the CPAN section on that wiki page to last place, On 05.08.10 12:09, Karsten Bräckelmann wrote: Sure. You can. It's a wiki... you should know what I mean... :) marked as DO NOT INSTALL FROM CPAN UNLESS YOUR DISTRO DOESN'T PROVIDE SPAMASSASSIN -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 42.7 percent of all statistics are made up on the spot.
X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
Hi, 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? 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. So why am I getting 3.2.3 still in the header of newly received mails? 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--tp29351374p29351374.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 14:18 -0700, Happy Chap wrote: Hi, 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? I think that's a mailscanner bug... There has been some discussion on this list about this in the past... -- Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX www.austinenergy.com
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
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... Hmmmthanks 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.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
Happy Chap wrote: 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: /usr/bin/spamd /usr/sbin/spamd and also /usr/bin/X11/spamd OK, I've got a little further: /usr/bin/spamd is v3.3.1 /usr/sbin/spamd is v3.2.3 /usr/bin/X11/spamd is also v3.3.1 so I can see what you're saying. Rather than upgrade the existing SpamAssassin installation, by using CPAN I've ended up installing a new one in a different location. However, I'm still confused because the command in the procmailrc is /usr/bin/spamc and if I do a /usr/bin/spamc --version from the bash prompt that tells me it's SpamAssassin Client version 3.3.1 - so why is the SpamAssassin X-Spam-Checker-Version coming up as 3.2.3 when I'm calling it through /usr/bin/spamc (which claims to be v3.3.1)? 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--tp29351374p29351698.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 14:54 -0700, Happy Chap wrote:
Karsten Bräckelmann wrote:
Hmmmthanks 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!!).
Mixing packages and CPAN never is a good idea...
No I didn't uninstall 3.2.3 - I didn't know I was supposed to.
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!)
What installed that init script? I believe SA built from CPAN does
*not*, so that's either your creation, or more likely part of the distro
supplied package (I assume) that provides SA 3.2.
And, well, in there you probably find the full path of the spamd
executable actually started.
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?
I was merely pointing out, that you now have two instances of each
executable part of SA. spamc, spamd, sa-update, sa-learn, spamassassin.
It all depends on your $PATH, which one is used -- or the path
hard-coded into the calling (init) script.
The idiots guide? Let's start by never have two different versions
installed. :)
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).
spamc (the lightweight SA client) does not call spamd (the daemon). It
merely talks to the daemon, which is already running -- started by your
init script.
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
Happy Chap wrote: OK, I've got a little further: /usr/bin/spamd is v3.3.1 /usr/sbin/spamd is v3.2.3 /usr/bin/X11/spamd is also v3.3.1 Is it as simple as I just need to edit my /etc/init.d/spamd script to amend any references in their from /usr/sbin/spamd to /usr/bin/spamd ? I thought about just giving it a try, but I'm just weary about making it worse now! 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--tp29351374p29351762.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 15:02 -0700, Happy Chap wrote:
Happy Chap wrote:
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: /usr/bin/spamd /usr/sbin/spamd and also /usr/bin/X11/spamd
OK, I've got a little further:
/usr/bin/spamd is v3.3.1
/usr/sbin/spamd is v3.2.3
/usr/bin/X11/spamd is also v3.3.1
so I can see what you're saying. Rather than upgrade the existing
SpamAssassin installation, by using CPAN I've ended up installing a new one
in a different location.
Err, any chance the (distro) package provided SA once had a link
from /usr/bin/spamd to /usr/sbin/spamd, where it actually lives? And the
former has been overwritten by the CPAN install?
However, I'm still confused because the command in the procmailrc is
/usr/bin/spamc and if I do a /usr/bin/spamc --version from the bash prompt
that tells me it's SpamAssassin Client version 3.3.1 - so why is the
SpamAssassin X-Spam-Checker-Version coming up as 3.2.3 when I'm calling it
through /usr/bin/spamc (which claims to be v3.3.1)?
The version in that header is NOT added, nor affected by the spamc
version. The daemon, spamd, that does the actual processing, also adds
that header.
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
Karsten Bräckelmann-2 wrote: Mixing packages and CPAN never is a good idea... OK, lesson learnt! Karsten Bräckelmann-2 wrote: What installed that init script? I believe SA built from CPAN does *not*, so that's either your creation, or more likely part of the distro supplied package (I assume) that provides SA 3.2. And, well, in there you probably find the full path of the spamd executable actually started. Yes, it must have been part of the original SuSE build. However, taking the hint, I've killed the old spamd daemons, edited the init.d/spamd script to point to /usr/bin/spamd (the new version) and restarted the daemon and all *appears* to be working OK, fingers crossed, and X-Spam-Checker-Version is now reporting v3.3.1 Karsten Bräckelmann-2 wrote: I was merely pointing out, that you now have two instances of each executable part of SA. spamc, spamd, sa-update, sa-learn, spamassassin. It all depends on your $PATH, which one is used -- or the path hard-coded into the calling (init) script. The idiots guide? Let's start by never have two different versions installed. :) Again, lesson learned. I'm older wiser today than I was yesterday! One final question - do I just delete the old spamd from /usr/sbin now to avoid any confusion (I've never uninstalled anything under Linux before)? Thanks for your help Karsten - much appreciated. -- View this message in context: http://old.nabble.com/X-Spam-Version-Checker-reports-3.2.3-but-running-3.3.1---Why--tp29351374p29351844.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 15:10 -0700, Happy Chap wrote:
/usr/bin/spamd is v3.3.1
/usr/sbin/spamd is v3.2.3
/usr/bin/X11/spamd is also v3.3.1
Is it as simple as I just need to edit my /etc/init.d/spamd script to amend
any references in their from /usr/sbin/spamd to /usr/bin/spamd ?
I guess so. You can quickly test, and revert the init script, if it
doesn't work out.
I thought about just giving it a try, but I'm just weary about making it
worse now!
Well, you got to clean it up anyway. ;)
Uninstalling the old version (Installed by distro packages, right!? You
never confirmed this.) would be a very good idea. But beware, if both
versions actually share some prefix and thus files, you might end up
with some crucial bits removed by the package manager, which have been
overwritten by the CPAN install. If so, after uninstalling the old,
definitely do re-install the new.
Oh, and just in case -- you DID run sa-update with its 3.3 version,
didn't you? Otherwise, you'll end up with no rules after uninstalling
3.2.
Something like /var/lib/spamassassin/3.003001/ should exist. 'man
spamassassin' knows about the exact location -- if it's the 3.3 one.
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
Karsten Bräckelmann-2 wrote: I guess so. You can quickly test, and revert the init script, if it doesn't work out. Yes, that *appears* to have worked. Karsten Bräckelmann-2 wrote: Well, you got to clean it up anyway. ;) Uninstalling the old version (Installed by distro packages, right!? You never confirmed this.) would be a very good idea. But beware, if both versions actually share some prefix and thus files, you might end up with some crucial bits removed by the package manager, which have been overwritten by the CPAN install. If so, after uninstalling the old, definitely do re-install the new. Maybe I'll just delete the old spamd executable in /usr/sbin so it can't be called by mistake rather than risking breaking any dependencies. Karsten Bräckelmann-2 wrote: Oh, and just in case -- you DID run sa-update with its 3.3 version, didn't you? Otherwise, you'll end up with no rules after uninstalling 3.2. Something like /var/lib/spamassassin/3.003001/ should exist. 'man spamassassin' knows about the exact location -- if it's the 3.3 one. Yes, I did run sa-update after installing the 3.3 version (I read that in the change log - so I do try and follow the guides, it just didn't say don't install from CPAN if you have a distro version!) and I do have /var/lib/spamassassin/3.003001 as well. I guess I can just delete the /var/lib/spamassassin/3.002003 now as well as that should be being used anymore? Thanks again for all your help. David. -- View this message in context: http://old.nabble.com/X-Spam-Version-Checker-reports-3.2.3-but-running-3.3.1---Why--tp29351374p29351910.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 15:23 -0700, Happy Chap wrote:
Karsten Bräckelmann wrote:
What installed that init script? I believe SA built from CPAN does
*not*, so that's either your creation, or more likely part of the distro
supplied package (I assume) that provides SA 3.2.
And, well, in there you probably find the full path of the spamd
executable actually started.
Yes, it must have been part of the original SuSE build. However, taking the
hint, I've killed the old spamd daemons, edited the init.d/spamd script to
point to /usr/bin/spamd (the new version) and restarted the daemon and all
*appears* to be working OK, fingers crossed, and X-Spam-Checker-Version is
now reporting v3.3.1
I was merely pointing out, that you now have two instances of each
executable part of SA. spamc, spamd, sa-update, sa-learn, spamassassin.
It all depends on your $PATH, which one is used -- or the path
hard-coded into the calling (init) script.
The idiots guide? Let's start by never have two different versions
installed. :)
Again, lesson learned. I'm older wiser today than I was yesterday!
One final question - do I just delete the old spamd from /usr/sbin now to
avoid any confusion (I've never uninstalled anything under Linux before)?
Well, I definitely would uninstall the package, as in 'rpm -e' or
whatever that specific version and flavor of SuSE prefers as a magical
package manager and interface (it changed). rpm will work, but there
most likely are more than a single RPM to remove.
Probably spamassassin, spamd, or similarly named, maybe more.
Thanks for your help Karsten - much appreciated.
However, beware! Keep in mind my earlier note about packages removing
vital stuff in your current environment. Uninstalling some spamd
package also will flame your current init script. It is distro provided,
not installed by CPAN. Keep a copy...
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: X-Spam-Version-Checker reports 3.2.3 but running 3.3.1 - Why?
On Wed, 2010-08-04 at 15:32 -0700, Happy Chap wrote:
Karsten Bräckelmann-2 wrote:
Uninstalling the old version (Installed by distro packages, right!? You
never confirmed this.) would be a very good idea. But beware, if both
versions actually share some prefix and thus files, you might end up
with some crucial bits removed by the package manager, which have been
overwritten by the CPAN install. If so, after uninstalling the old,
definitely do re-install the new.
Maybe I'll just delete the old spamd executable in /usr/sbin so it can't be
called by mistake rather than risking breaking any dependencies.
No distro provided RPM package for SA possibly can be a dependency. Just
don't also uninstall their dependencies, like Perl Modules.
Yes, I did run sa-update after installing the 3.3 version (I read that in
the change log - so I do try and follow the guides, it just didn't say don't
install from CPAN if you have a distro version!) and I do have
/var/lib/spamassassin/3.003001 as well. I guess I can just delete the
/var/lib/spamassassin/3.002003 now as well as that should be being used
anymore?
Yes, the 3.002003 one can be removed, if you are actually running SA 3.3
spamd.
--
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;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
