Re: [Evolution] Re: junk filtering

[guenther <guenther rudersport de>]

> > The question is not whether you can use the buttons. Yes, they are
> > always enabled and do "something".
> >
> > The problem is when you want to use it to learn ham. Apparently it was
> > not designed for that, it looks like it was designed to undo a previous
> > "junk"-button-press, because only then something actually happens, being
> > the bayes database being updated. If you push "not junk" on a random
> > message, the message doesn't get learned as "ham".
>
> So this is a big issue, currently on HEAD, we have either the "Junk" or
> the "Not Junk" button, based on wether the messages has been marked junk
> or not. We actually needs to discuss this further. Am CCing Srini for
> his comments on this.

Revert that commit immediately.

This is a bad idea. Really. All you gain is a few pixels in the toolbar.
But if this UI change is introduced in 2.6, it will be harder for the
developers and confusing to the users to get the other button in again.

Questions regarding "Junk filtering not working" majorly impacted by a
badly (if at all) trained Bayes are common these days. To make SA more
effective, the user needs to train Bayes. So there *must* be a way to
train it. The user has to be able to make SA learn *any* mail marked as
either Ham or Spam previously.

Automatic learning is *not* done for any mail. The score has to be above
(or lower than) a threshold, which is way more extreme than the "spam
limit".

For Bayes to kick in SA needs to be trained 200 Spam and Ham *each*.

These buttons should not be "mark as" Ham/Spam, but "learn as" Ham/Spam.

...guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
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; }}}