https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3364
Mark Martinec <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Use of customized header |[review] Use of customized
|yields "nan" for _HITS_ |header yields "nan" for
|variable |_HITS_ variable
--- Comment #16 from Mark Martinec <[EMAIL PROTECTED]> 2008-10-16 06:45:34 PST
---
After Benedict also reported a seemingly unrelated source
of NaN floating-point values ceeping into timing data:
spamd[1321]: plugin: eval failed:
Sort subroutine didn't return a numeric value
at /usr/share/perl5/Mail/SpamAssassin/AsyncLoop.pm line 278.
and telling that he is running SpamAssassin on a UML virtual
machine (http://user-mode-linux.sourceforge.net/), a Google
search revealed a bug in the UML virtual machine:
http://fixunix.com/openssl/
518688-re-uml-devel-dev-random-problems-fp-registers-corruption.html
and a fix for it (February 2008):
UML - Fix FP register corruption
http://kerneltrap.org/mailarchive/linux-kernel/2008/2/12/829244
Benedict wrote:
> That could well be it. I was running a 2.6.25.4 UML kernel.
> I don't know if that specific kernel version had that error but it seems so.
> I've compiled a new 2.6.27 UML kernel and rebooted the virtual machine with
> the new kernel. Let's see what happens next :)
and two days later:
> At the moment, so far so good. I haven't seen any nan scores anymore and
> all the emails are with a score > 4 are now flagged as spam like i want.
So it seems the mistery is explained, at least in Benedict's case.
Still, a NaN may well come from a third-party plugin, and as my proposed
patch was able to detect and sanitize a NaN source in Benedict's case,
I propose the patch to be included into 3.2.6. (it already is in the 3.3 cvs
for the last couple of days).
The patch
"Deal with NaN in AutoWhitelist and PerMsgStatus, fix a bad AWL record)"
has the following function:
- prevent and warn of an attempt of a plugin to add a NaN to the score
(thus destroying what was collected so far and polluting final result);
- prevent a NaN from entering an AWL database, polluting further SA runs;
- sanitize a NaN in a fetched AWL record by resetting a record,
when such record happens to be in a database (e.g. from earlier bugs).
Moving into a review state, 2 votes needed...
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
