https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6856
Priority: P2
Bug ID: 6856
Assignee: [email protected]
Summary: Mass check is throwing a "1/8" isn't numeric error
Severity: normal
Classification: Unclassified
OS: Windows 7
Reporter: [email protected]
Hardware: PC
Status: NEW
Version: unspecified
Component: Masses
Product: Spamassassin
Reported on 10/24 by Marc Andre Selig and on 10/25 by Jari Fredriksson, lots of
warning messages from auto-mass-check.sh
> Syncing nightly_mass_check
> + ./mass-check --hamlog=ham-mas.log --spamlog=spam-mas.log -j 1 --progress
> --reuse ham:dir:/home/sacheck/corpora/ham
> spam:dir:/home/mas/Home/Mail/archives/spam
> status: starting scan stage now: 2012-10-24
> 11:00:19 AM
> status: completed scan stage, 7638 messages now: 2012-10-24
> 11:00:21 AM
> status: starting run stage now: 2012-10-24
> 11:00:21 AM
> Argument "1/8" isn't numeric in numeric le (<=) at
> /home/sacheck/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/PerMsgStatus.pm
> line 2441.
> Argument "1/8" isn't numeric in numeric le (<=) at
> /home/sacheck/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/PerMsgStatus.pm
> line 2441.
> Argument "1/8" isn't numeric in numeric le (<=) at
> /home/sacheck/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/PerMsgStatus.pm
> line 2441.
> [... 7587 identical lines omitted ...]
> Argument "1/8" isn't numeric in numeric le (<=) at
> /home/sacheck/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/PerMsgStatus.pm
> line 2441.
> status: completed run stage now: 2012-10-24
> 11:29:23 AM
> + LOGLIST=' ham-mas.log spam-mas.log'
> + set +x
> rsync -qPcvz ham-mas.log spam-mas.log [email protected]::corpus/
>
Per Jari: Same here. I have 25000+ rows with this message in my cron job email
from masscheck. It seems that every email in my corpus triggers this.
Checking the nightly mass checks that run on SA's zones, we do NOT have this
error. Likely something with IPv6, trusted networks and/or a perl module,
perhaps?
This is the logic with the error:
# ensure that rule values always result in an *increase*
# of $self->{tests_already_hit}->{$rule}:
my $value = $params{value};
if (!$value || $value <= 0) { $value = 1 }
--
You are receiving this mail because:
You are the assignee for the bug.
