Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: CRM114 Mailfilter and spam.el
Date: Fri, 02 Apr 2004 18:04:49 +0200	[thread overview]
Message-ID: <87vfkigyce.fsf@virgil.koldfront.dk> (raw)
In-Reply-To: <87wu4ysxum.fsf@emptyhost.emptydomain.de>

On Fri, 02 Apr 2004 08:22:25 +0200, Kai wrote:

> asjo@koldfront.dk (Adam Sjøgren) writes:
>> * If a spam is misclassified as ham, I would like to mark that
>> message in some way, so that it is moved to nnml:spam and
>> mailfilter.crm is called with --learnspam on it.

> I think you want to set spam-process-ham-in-spam-groups for this
> one.

>> * If a ham is misclassified as spam, and therefore is split into
>> nnml:spam, I would like to move it to the correct group and have
>> mailfilter.crm called on it with --learnnonspam.

> But I can't find spam-process-spam-in-ham-groups. Hm.

Okay, I got it almost working (by reading the documentation one more
time).

My understanding so far is this:

 * I want all my groups to be unclassified - because I only want to
   train on errors (marking them by hand). I never want to train on
   properly classified ham nor spam.

 * On the topic that contains all my normal email-groups, I've set
   these parameters:

    ((spam-process
      '(spam spam-use-crm114))
     (spam-process-destination . "nnml:spam"))

   This means that if spam ends up in one of my normal email-groups, I
   mark it with M-d ($), and it crm114 is called to learn it as spam,
   and it is moved to nnml:spam.

   Success! This is what I want, and it works.

 * On my nnml:spam-group (where spam is split to, and moved to as per
   above) I've set these parameters:

    ((spam-process
      '(ham spam-use-crm114))
     (ham-process-destination . "nnml:normal")
     (spam-process-destination . "nnml:spam")
     (ham-marks
      (gnus-ticked-mark))

   What I want to achieve with this is: When a ham ends up in nnml:spam,
   I tick it (!). When I leave the group, crm114 should learn it as
   ham, and the article should be moved to nnml:normal[1].

   This only works partially: The ticked articles are processed by
   crm114 to be learned as ham (fine), but the articles are not moved
   to nnml:normal - they stay in nnml:spam.

   (I guess the spam-process-destination should be removed, as it
    isn't used).

 * My global variables are set like this:

    (setq
     ; Only process each article once:
     spam-log-to-registry t
     ; Only process spam in nonspam groups (i.e. Train On Error only):
     spam-move-spam-nonspam-groups-only t
     ; All my groups are unclassified, I should remove this one:
     spam-process-ham-in-spam-groups t
     ; Process ham in ham and unclassified groups:
     spam-process-ham-in-nonham-groups t
     ; I want ham to be unread when moved out (it never is, but that's
     ; what I would like if it did move):
     spam-mark-ham-unread-before-move-from-spam-group t
     ; CRM114 Mailfilter (I will submit a patch):
     spam-use-crm114 t
     spam-crm114-path "/home/asjo/crm114.pl" ; (for debugging)
     spam-crm114-database-directory "--fileprefix=/home/asjo/.crm114/")

   And I use (: spam-split) in my fancy split-rules.

This is very cool - it's beginning to make sense to me _and_ it almost
works :-)

I've only got the "ham-marked articles in nnml:spam should be moved as
well as processed"-problem left.


  Best regards,

    Adam

[1]: If the articles I mark as ham in nnml:spam could be 1) learned as
     ham by crm114 and then 2) respooled, that would be even better
     than 2) moved to nnml:normal.

-- 
 "Mr. Cotton's... parrot. Same question."                     Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2004-04-02 16:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 20:54 Adam Sjøgren
2004-04-02  6:22 ` Kai Grossjohann
2004-04-02 16:04   ` Adam Sjøgren [this message]
2004-04-03 13:28     ` Kai Grossjohann
2004-04-03 14:01       ` Adam Sjøgren
2004-04-05 13:21         ` Ted Zlatanov
2004-04-02 16:06   ` Adam Sjøgren
2004-04-02 17:14     ` Ted Zlatanov
2004-04-03 21:10       ` Adam Sjøgren
2004-04-03 21:19         ` Adam Sjøgren
2004-04-03 21:48           ` Adam Sjøgren
2004-04-03 21:58             ` Adam Sjøgren
2004-04-03 13:29     ` Kai Grossjohann
2004-04-03 13:49       ` Adam Sjøgren
2004-04-06  8:12         ` Kai Grossjohann
2004-04-06 21:40           ` Adam Sjøgren
2004-04-02 16:10   ` Jody Klymak
2004-04-02 17:07   ` Ted Zlatanov
2004-04-02 17:06 ` Ted Zlatanov
2004-04-02 17:26   ` Adam Sjøgren
2004-04-02 17:44     ` Ted Zlatanov
2004-04-03 14:22       ` Adam Sjøgren
2004-04-03 14:24         ` Adam Sjøgren
2004-04-03 23:59 ` Adam Sjøgren
2004-04-04  1:59   ` Jesper Harder
2004-04-04 13:07     ` Adam Sjøgren
2004-04-05 13:24       ` Ted Zlatanov
2004-04-05 15:50         ` Jesper Harder
2004-04-06 21:36       ` Adam Sjøgren
2004-05-20 18:39         ` Ted Zlatanov
2004-05-20 19:19           ` Adam Sjøgren
2004-05-22 23:44             ` Lars Magne Ingebrigtsen
2004-05-23 13:44               ` Adam Sjøgren
2004-05-26 16:23             ` Ted Zlatanov
2004-05-26 20:30               ` Adam Sjøgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vfkigyce.fsf@virgil.koldfront.dk \
    --to=asjo@koldfront.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).