Re: spam.el reporting and moving ham out of spam groups.

[asjo@koldfront.dk (Adam Sjøgren)]

On Wed, 26 May 2004 14:46:27 +1000, Daniel wrote:

>> I think spam.el would be doing "what-I-mean" more if it
>> ham-processed messages marked as ham in unclassified groups in
>> addition to spam groups (that is, all non-ham groups).

> That is also undesirable to me, since I want to 'train on errors'
> for non-spam as well. :)

I don't understand that. I train on error for both spam and ham.

With what I described, messages marked as ham get ham-processed
whenever they are not in a ham-group.

If a message is in a ham-group it is not an error when the message is
ham?

(That is, you can't "train on error" on a ham-message when it's
correctly classified and put in a ham-group, right?)

>> (If I mark something as ham, I want it ham-processed (unless it is
>> in a ham-group, then I've probably marked it by mistake O:-))

> ...unless there is some explicit ham mark I have missed, "marked as
> ham" means "read, killed or scored down", at least by default...

Oh, I've set:

 (ham-marks
  (gnus-ticked-mark))

so I just use that and nothing else. Maybe that's skewing/obscuring my
comments.


Basically my setup is:

      Incoming email

      Does spam.el think it's spam?

 Yes:                      No:

 Put in nnml:spam          Do normal splitting

a) If a message in nnml:spam is ham, I mark it as ham, CRM114 is
   trained on it, and the message is run through normal splitting.

b) If a message not in nnml:spam is spam, I mark it as spam, CRM114 is
   trained on it, and the message is moved to nnml:spam.

I'm probably missing your points because this is simpler/more naïve
than your setup.


  Best regards,

-- 
 "Just the words?" What a terrible to thing to say            Adam Sjøgren
  about writing!                                         asjo@koldfront.dk