-----Original Message----- From: Mark Howells Sent: 01 December 2003 10:29 To: spambayes@python.org Subject: RE: [Spambayes] Clasification difficulties using pop3proxy / sb_server

Ooops - I've just looked at my question again and realise that the question looks ridiculous ;) What I _meant_ to write, was that I get some message that are classified as 'unsure' when the declared spam probability is 0.8 or higher. i.e. the spam rating is higher than the spam threshold.

...

Clues! Clues! Give us the clues!

Here's one that (with no training since it was classified) has a spam probability of 0.84, and is classified as unsure. The spam cutoff is 0.8 I'm guessing now, but it's possible that the classification of the 'unsure' token (see earlier part of thread) may have taken it over the brink of 0.8 eg. It may have had a rating of 0.79, been classified (correctly) as unsure. had the (spammy) unsure token added and is now showing as 0.84. In which case it's the clues production thats incorrect. Any ideas? Mark -- Outgoing mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.203 / Virus Database: 261.3.2 - Release Date: 11/27/2003