DSPAM is going burko again

[antic]

Just today I have received an email marked *****SPAM***** which has never been marked *****SPAM***** before.

Has DSPAM been diddled with again because of the recent HSphere upgrade? In the header was this:

X-DSPAM-Result: Spam
X-DSPAM-Processed: Sun Oct 28 18:00:18 2007
X-DSPAM-Confidence: 0.5000
X-DSPAM-Probability: 0.9900
X-DSPAM-Signature: 47250672305471825385791
X-DSPAM-User: [my email address]
X-DSPAM-Factors: 15,
	X-OriginalArrivalTime*Oct, 0.99000,
	Foundations, 0.99000,
	Bernie, 0.01000,
	X-OriginalArrivalTime*Oct+2007, 0.99000,
	<mark, 0.01000,
	Received*dspam2.m****here.biz+(Postfix), 0.01000,
	Received*by+dspam2.m****here.biz, 0.01000,
	Date*12+0900, 0.99000,
	to+David, 0.01000,
	Jackie, 0.99000,
	to+James, 0.99000,
	to+Steve, 0.01000,
	of+Grant, 0.99000,
	au>, 0.01000,
	mp, 0.99000

Is it supposed to be giving 0.99 points to words like "James" etc? "mp"? "X-OriginalArrivalTime*Oct+2007"????

What's going on in DSPAM's wee little peanut brain now?

 

[timruns]

I seem to have had a lot of emails all of a sudden start getting marked as well... Like Antic, which had never been marked before...
Tim

 

[antic]

C'mon Jodo, spill the beans... why would the DSPAM the rules have suddenly changed? Seems to have just happened after the recent HSphere update.

 

[tanmaya]

dspam was never related to Hsphere in any way apart from spamassassin that sits on mailservers to actually mark spam. As i've mentioned in the past, dspam is trained on weekends and this is just what we did.
I've also trained the signature in your header as false positive.
if both of you can report all false postives today it will be great or we will have to wait for false positives received on coming weekend.