tri-state transition [was: bogofilter-0.93.0 - Significant Changes]

[Robin Bowes]

David Relson wrote:
> On Sun, 07 Nov 2004 10:03:11 +0000 Robin Bowes wrote:
>>
>>Just an idea, but wouldn't it make the upgrade easier if the tri-state
>>mode messages were "Yes, "No" and "Unsure"?
>>
> 
> Good point!  However there are two things going on here.  Adding the
> third "Unsure" state is one and having better labels is the other, i.e.
> "Spam" and "Ham" rather than "Yes" and "No".
> 
> If you'd rather make the transition in smaller steps, enable the
> "spamicity_tags = Yes, No, Unsure" line in bogofilter.cf.

I've just upgraded - looks like I was the first to download from 
sourceforge!

In the end I went with the new tags and modified my maildrop script to 
look for "X-Bogosity: Spam".

I'm not sure that the "Unsure" status adds much to my situation. Let me 
discuss...

I run bogofilter in pass-through mode (-p) in a maildrop script, 
filtering on the X-Bogosity header line. Spam (X-Bogosity: Yes|Spam) is 
put in the users' SPAM folder. Everything else (i.e. X-Bogosity: 
No|Ham|Unsure) is delivered as normal.

I also use the -u option so messages are added to the wordlist 
automatically.

If any spam is missed, the user can drop the message in a 
SPAM/Undetected folder from where it is re-processed from a script run 
from cron which essentially runs the message through bogofilter with the 
-Ns options.

Any messages mistakenly classified as Spam can be dropped in a 
Spam/Misdetected folder from where they are re-processed using 
bogofilter with the -Sn options.

So, I'm not sure how the "Unsure" classification contributes to my 
configuration. I may even consider reverting to the binary classification.

Any suggestions?

R.
-- 
http://robinbowes.com