[spambayes-bugs] [ spambayes-Bugs-972359 ] some 100% SPAM sent to unsure

SourceForge.net noreply at sourceforge.net
Mon Jun 28 03:21:43 EDT 2004

Bugs item #972359, was opened at 2004-06-14 12:12
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 

Category: Outlook
Group: Binary 1.0rc1
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan Zenchelsky (dzenc)
Assigned to: Mark Hammond (mhammond)
Summary: some 100% SPAM sent to unsure

Initial Comment:
(This is a continuation of Bugs item #923921.  I am 
opening a new bug report so that I can upload related 

About 5-10% of all 100%-spam gets shifted to the
"Possible Spam" folder rather than the "Spam" folder. 


I received a message which was sent to the "unsure" 
folder.  I then ran "show spam clues" on it, which 
showed that it was 100% SPAM (see attached file).  

I then manually ran "filter messages..." on the unsure 
folder and it correctly detected the message as SPAM 
and moved it to the correct folder.

*No* training was done between the time the message 
arrived and the time that I performed these steps.



>Comment By: Mark Hammond (mhammond)
Date: 2004-06-28 17:21

Logged In: YES 

This will be an error in our 'content-type' magic.  If I
look at the headers for this message, as shown by Outlook's
View->Options, I see:

Microsoft Mail Internet Headers Version 2.0
Received: from mx56.dadoihag.us ([]) by
proxy.danz.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 13 Jun 2004 18:39:09 -0700
From: "United Coalition" <SarahAllen at mx56.dadoihag.us>
To: " " <danz at danz.com>
Subject:  1 Minute Mortgage Application Here
Date: Sun, 13 Jun 2004 20:39:07 -0600
Message-ID: <lyadopvyxqhkvziyyttf at mx56.dadoihag.us>
MIME-Version: 1.0
Content-Type: multipart/alternative;
Return-Path: SarahAllen at mx56.dadoihag.us
X-OriginalArrivalTime: 14 Jun 2004 01:39:10.0757 (UTC)

Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

That doesn't look right (to me) for the headers, and I
suspect is what is causing the tokenizer to not see all the
tokens when filtered, but it *does* see them all for 'spam


You can respond by visiting: 

More information about the Spambayes-bugs mailing list