On 10/28/18 6:13 AM, Henrik K wrote:
On Sun, Oct 28, 2018 at 05:43:46AM -0500, Dave Jones wrote:
My ena-week2-3 masscheckers have been having this problem below for a couple
of months now but I haven't had the time to figure this out.
Why didn't you post this immediately. :-)
I have been swamped at my day job for the past 4 months basically not
had a day off in months. Like I said below. This wasn't a problem
until recently when we dropped below the masscheck limits and rule
updates stopped.
could be related to all of the work Kevin did to get SA 3.4.2 out based on
timing.
...
near "s/\t/ /gr"
This requires perl 5.14.
They are running CentOS 6.10 and perl v5.10.1.
I would gladly update the perl on those boxes but I can't upgrade the OS
due to some software running on it that doesn't support systemd yet. I
had plans to upgrade this software over the summer but the company I
work for got a new contract in May which has taken up all of my time.
Masschecking uses trunk, which officially requires perl 5.14 and even
enforces that during install, so that's what you (we) should use. I don't
think there are any general problems using older, but you should really
upgrade so we don't get any unicode related differences between masschecker
results.
If there is a good repo for upgrading the system perl on a C6 box
correctly, I would do it. I try to install RPMs as much as possible
from EPEL for any perl modules but there are some that came from CPAN.
I don't want to break the existing perl program on those 2 VMs but I
would give it a try and rollback the changes if anything became broken.
As I have said before, I am not a perl person so I would have to take
things slowly where I am normally pretty fast.
In the mean time, I downgraded the wrap function again for pre-5.14 method:
http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Util.pm?r1=1844277&r2=1845014
I noticed. Thank you.
I think we should try to refrain from using newer perl functions until 4.0.0
is officially released..
