On Mon, 2008-10-13 at 17:39 +0200, Mark Martinec wrote:
> > Thing is, what is causing the nan?
>
> My guess is that a NaN somehow got into your AWL database.
Things are much more complicated, or rather weird, than that.
According to Benedict's reports and pasted snippets, he got an NaN score
for at least 3 rules: FROM_ILLEGAL_CHARS, AWL, MSOE_MID_WRONG_CASE
Also, it appears that he actually is using custom headers. The initial
snippets showed a stray " char at the beginning of X-Spam-Status. The
last paste does not show that header at all.
It might be noteworthy, that X-Spam-Flag and the verbose X-Spam-Report
are either added unconditionally, or this is just a side effect when
comparing to the spam threshold (not exceeding the threshold, thus "no",
but yet not below the threshold, thus not excluded).
Benedict, since I asked about custom headers before, it might be a good
idea to carefully check the config and answer my previous question.
Since you're not using custom rules, but change scores, you likely
copied (read: inherited) that part from your previous cf files. How
carefully did you check this and *any* customization?
Also, please do check the config for invisible, stray chars, as I
pointed out before. This includes user_prefs, if any. At that note: Does
this affect only a single user (if using per user settings)?
A wild guess: Since the affected rule/score varies wildly, might the
culprit by any chance be bad RAM?
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
