[opensuse] Why is our SpamAssassin version so old?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, My SpamaAssassin headers say: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor It is dated 2011. I would think that openSUSE 13.1 would have a release dated 2013 at least... Yes, I know that devel:languages:perl has the latest version (3.4.0), but my question is why the default version is so old. Was there a problem? The mail:server repo does not have any version :-? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO38osACgkQtTMYHG2NR9XZNQCfSkR10m48ECBXR1cHz29Y0+Q3 9KoAn3HyOa0HxXBccK2ovcOnnUvbUpH/ =rG8j -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 05/07/14 08:41, Carlos E. R. escribió:
Yes, I know that devel:languages:perl has the latest version (3.4.0), but my question is why the default version is so old. Was there a problem?
The most likely reason is: package had no maintainer or maintainer had no time to work on it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 05 Jul 2014, Cristian Rodríguez wrote:
El 05/07/14 08:41, Carlos E. R. escribió:
Yes, I know that devel:languages:perl has the latest version (3.4.0), but my question is why the default version is so old. Was there a problem?
The most likely reason is: package had no maintainer or maintainer had no time to work on it.
Nope. As d:l:perl is devel project for Factory (which has 3.4.0!) SA is _actively_ maintained. The reason is: that normally _NO_ package gets a version update during the support phase of a package. Ever. Patched yes. Exceptions being security and "data loss" (or similar) updates that cannot be backported (easily enough for the devel-team). SA does have a (appointed not "inherited") bugowner, so ... And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended. Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different). So, zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_13... would solve your problem (they currently build for 12.2-Factory) -dnh -- In the old days, it was very simple: "You shoot us, we shoot you." Then, after WW II, we had the IRA in the 80ies, it was: "They blow us up, and we shoot back." And now, in the days of friendly fire, in Iraq, it's: "They blow themselves up and we shoot each other." -- Omid Djalili Show 1x06, on War -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-05 18:17, David Haller wrote:
And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended.
Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different).
That was not my point. What I posted was about this line:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
The "problem" is not the version number, but the year. The version shipped with 13.1 in year 2013 has a timestamp dated 2011, that is, two full years before. That's the reasons I was saying that the SpamAssassin version we have is too old. John Andersen pointed to me that what is important really is the ruleset, and that one is recent - although I don't know of a way to know its version (and Patrick Shanahan said how to update that part). And he (John) also said "SA 3.3.2 was the current version up until February of this year". Which explains why 13.1 got it. Still, that the year stamp says "2011" is not good looking.
So,
zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_13...
would solve your problem (they currently build for 12.2-Factory)
It is confusing (at least to me) to find SA in a language repository, and not in the Server:Mail repository. Why is it there? The obvious implication is that updating SA may need to update the whole of Perl. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO7008ACgkQtTMYHG2NR9XBVgCbBfY3wRiHTkKVbA2zVc+AcB+C v1sAnimdeceR68nbKpbalIlMPGLP0iVJ =SQyx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-05 18:17, David Haller wrote:
And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended.
Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different).
That was not my point. What I posted was about this line:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
The "problem" is not the version number, but the year. The version shipped with 13.1 in year 2013 has a timestamp dated 2011, that is, two full years before. That's the reasons I was saying that the SpamAssassin version we have is too old.
John Andersen pointed to me that what is important really is the ruleset, and that one is recent - although I don't know of a way to know its version (and Patrick Shanahan said how to update that part).
And he (John) also said "SA 3.3.2 was the current version up until February of this year". Which explains why 13.1 got it.
Still, that the year stamp says "2011" is not good looking.
Maybe not, but it's correct.
It is confusing (at least to me) to find SA in a language repository, and not in the Server:Mail repository. Why is it there?
The obvious implication is that updating SA may need to update the whole of Perl.
Which is a possiblity if some SA version requires a newer Perl version. -- Per Jessen, Zürich (14.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jul 8, 2014 at 7:17 AM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-05 18:17, David Haller wrote:
And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended.
Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different).
That was not my point. What I posted was about this line:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
The "problem" is not the version number, but the year. The version shipped with 13.1 in year 2013 has a timestamp dated 2011, that is, two full years before. That's the reasons I was saying that the SpamAssassin version we have is too old.
John Andersen pointed to me that what is important really is the ruleset, and that one is recent - although I don't know of a way to know its version (and Patrick Shanahan said how to update that part).
And he (John) also said "SA 3.3.2 was the current version up until February of this year". Which explains why 13.1 got it.
Still, that the year stamp says "2011" is not good looking.
So,
zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_13...
would solve your problem (they currently build for 12.2-Factory)
It is confusing (at least to me) to find SA in a language repository, and not in the Server:Mail repository. Why is it there?
The obvious implication is that updating SA may need to update the whole of Perl.
the 'spamassassin' package contains the command line tools but the perl-Mail-SpamAssassin package is it's support libraries and contains the rules and given it's a perl module d:l:p is the appropriate top-level project. There are many package in devel:languages:* which one would think belong elsewhere and in many instances they are _links or _aggregates to top level devel projects. Sometime package live in language repos so dependencies are meet, the request-tracker package in d:l:perl which I maintain is a good example of that. I typically look at it as if it's written in perl, python, R, whatever, that toplevel devel project is where it should live. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jul 8, 2014 at 7:17 AM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-05 18:17, David Haller wrote:
And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended.
Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different).
That was not my point. What I posted was about this line:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
The "problem" is not the version number, but the year. The version shipped with 13.1 in year 2013 has a timestamp dated 2011, that is, two full years before. That's the reasons I was saying that the SpamAssassin version we have is too old.
John Andersen pointed to me that what is important really is the ruleset, and that one is recent - although I don't know of a way to know its version (and Patrick Shanahan said how to update that part).
And he (John) also said "SA 3.3.2 was the current version up until February of this year". Which explains why 13.1 got it.
Still, that the year stamp says "2011" is not good looking.
So, /etc/sysconfig/spamd zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_13...
-- Later, Darin
would solve your problem (they curr -- Later, Darinently build for 12.2-Factory)
It is confusing (at least to me) to find SA in a language repository, and not in the Server:Mail repository. Why is it there?
The obvious implication is that updating SA may need to update the whole of Perl.
FWIW there's already an sa-update cron script delivered, /etc/cron.daily/suse.cron-sa-update, for updating the rules. It's disabled by default but you can modify that via /etc/sysconfig/spamd.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO7008ACgkQtTMYHG2NR9XBVgCbBfY3wRiHTkKVbA2zVc+AcB+C v1sAnimdeceR68nbKpbalIlMPGLP0iVJ =SQyx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8 Jul 2014, at 7:17, Carlos E. R. wrote:
On 2014-07-05 18:17, David Haller wrote:
And BTW: 3.4.0 is the current upstream version, so all's ok and working as intended.
Carlos: if you want "up to date" packages, add the respective devel-repos to your portfolio. Most devel-projects do build for all supported distros (SLE* might be different).
That was not my point. What I posted was about this line:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
The "problem" is not the version number, but the year. The version shipped with 13.1 in year 2013 has a timestamp dated 2011, that is, two full years before. That's the reasons I was saying that the SpamAssassin version we have is too old.
There was no newer release version of SA until 2014. Anywhere. It is a bit silly silly to have it add that header to mail at all, but that's an optional local configuration choice. SA core releases are very rare because it is mature modular code in a mature modular ecosystem (Perl). SA gets a lot of its functionality from other Perl modules, a frequently update set of standard rules, optional 3rd-party rules, and optional local static rules & heuristics (e.g. Bayes and AWL DBs) so the core code doesn't need frequent updates. It's been very stable for many years, and that's a GOOD thing.
John Andersen pointed to me that what is important really is the ruleset, and that one is recent - although I don't know of a way to know its version (and Patrick Shanahan said how to update that part).
See the docs for sa-update. It can be made verbose about what it is doing, and it only actually performs an update when an updated ruleset is available.
And he (John) also said "SA 3.3.2 was the current version up until February of this year". Which explains why 13.1 got it.
Exactly, so the problem is...?
Still, that the year stamp says "2011" is not good looking.
Ageist! Just wait until *you* are over 3 years old! :) Not all software is so large and/or sloppy and/or immature as to require frequent changes. SA got a lot of tinkering and fixing in its first decade and doesn't have vast room for improvement remaining. The pace at which a piece of software changes naturally slows over time. That is a good thing, not a cosmetic problem.
So,
zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_13...
would solve your problem (they currently build for 12.2-Factory)
It is confusing (at least to me) to find SA in a language repository, and not in the Server:Mail repository. Why is it there?
Because SA is primarily a tree of Perl modules used by other software and it is NOT intrinsically part of a mail server.
The obvious implication is that updating SA may need to update the whole of Perl.
That's not how the Perl ecosystem typically works and has been made more rare in recent years with an accelerated pace of core 5.x releases. System distros have been keeping up with the new core releases better than module developers have been and there are not a lot of new functionality features in 5.10+ versions of Perl encouraging developers to abandon 5.8 support. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/5/2014 5:41 AM, Carlos E. R. wrote:
Hi,
My SpamaAssassin headers say:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on Telcontar.valinor
It is dated 2011. I would think that openSUSE 13.1 would have a release dated 2013 at least...
Yes, I know that devel:languages:perl has the latest version (3.4.0), but my question is why the default version is so old. Was there a problem?
The mail:server repo does not have any version :-?
To be fair, SA 3.3.2 was the current version up until February of this year, and the biggest change in 3.4.0 is ipv6 support. Most of SA development and maintenance in SA is not in the engine itself, but rather in the rule sets and plug ins, which get improved all the time, and are normally fetched by cron jobs. So the old engine really didn't need a lot changes. - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlO4V9wACgkQv7M3G5+2DLJVYACfXglmujVkSpCLJJ6vrgpVcobW FV4Ani7aCqynnhPmdVs0RzItywVhSCOz =0V65 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2014-07-05 at 12:54 -0700, John Andersen wrote:
On 7/5/2014 5:41 AM, Carlos E. R. wrote:
To be fair, SA 3.3.2 was the current version up until February of this year, and the biggest change in 3.4.0 is ipv6 support.
Most of SA development and maintenance in SA is not in the engine itself, but rather in the rule sets and plug ins, which get improved all the time, and are normally fetched by cron jobs. So the old engine really didn't need a lot changes.
I see. So I just run "sa-update" now and then. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO5Ro8ACgkQtTMYHG2NR9WJIgCfcEVX8q4v6OQB1krFEsZrh9JB 2JQAn35YxWn3zB55/BKeHM65PqSnyALw =wauP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [07-06-14 08:53]: [...]
So I just run "sa-update" now and then.
or perhaps a cron job once a day like (one lineer): sa-update --allowplugins -v --refreshmirrors&& sa-compile && /etc/init.d/spamd restart -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-06 14:57, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-06-14 08:53]: [...]
So I just run "sa-update" now and then.
or perhaps a cron job once a day like (one lineer): sa-update --allowplugins -v --refreshmirrors&& sa-compile && /etc/init.d/spamd restart
A bit excessive for me, using it in cron, perhaps - but I take note of the line, thanks :-) Weekly instead, maybe. But these things I like to do manually and see results. Why --allowplugins? They are not updated unless you specify them? And "sa-compile" is also required? I think I have done this before, and forgotten. Sigh. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-06-14 10:23]:
On 2014-07-06 14:57, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-06-14 08:53]: [...]
So I just run "sa-update" now and then.
or perhaps a cron job once a day like (one lineer): sa-update --allowplugins -v --refreshmirrors&& sa-compile && /etc/init.d/spamd restart
A bit excessive for me, using it in cron, perhaps - but I take note of the line, thanks :-)
Weekly instead, maybe. But these things I like to do manually and see results.
Why --allowplugins? They are not updated unless you specify them?
I have a few plugins but, as I set it up some years ago, I can always rely on my standard excuse, old-timers memroy. :^) I would have to research it again and really don't have the time unless the need becomes pressing.
And "sa-compile" is also required?
This one I do remember (I think), spamassassin is rule based and the rules are compressed for better speed.
I think I have done this before, and forgotten. Sigh.
As it becomes later in life with those things that are not done with some frequency :^) Lessons from high school in the 50's are *really* murkey. Welcome aboard :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Bill Cole -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Darin Perusich -
David Haller -
John Andersen -
Patrick Shanahan -
Per Jessen