On 11/30/2014 11:50 AM, Dave Pooser wrote:
On 11/30/14 12:34 PM, "Paul R. Ganci" <ga...@nurdog.com> wrote:
So just so I understand something is it expected that those of us with
RHEL 5.11 and RHEL 6.6 servers are expected to upgrade our perl versions
just for spamassassin's sa-update? The whole idea of running servers
with those versions of server software is for stability.
Yep. And the whole point of running SpamAssassin with sa-update is for
flexibility and agility. The two goals are necessarily in conflict. So...
Looks like you have a few options:
1) Don't run SA on RHEL
2) Run SA on RHEL but turn off sa-update and sacrifice automated reaction
to new spam in the interest of keeping your system static
3) Run SA on RHEL but upgrade perl and SpamAssassin using
third-party-packages or update from source
4) Run SA on RHEL with system perl and system SpamAssassin, run sa-update
with output redirected to /dev/null, and write your own monitoring script
to tell you if sa-update broke spamd
5) Run SA in some kind of container or VM so you can optimize for
spamassassin without tainting the purity of your RHEL install
You have to be joking if I am going to update my systems for sa-update.
It seems that this is a pretty much arrogant decision by spamassassin
development team. The problem is in sa-update. It should be fixed there.
--
Paul (ga...@nurdog.com)
