Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Green <cmg@sourcefire.com>
Subject: Re: spam.el and ham in a spam group
Date: Wed, 23 Jul 2003 11:38:17 -0400	[thread overview]
Message-ID: <m33cgxgsnq.fsf@radon.sfeng.sourcefire.com> (raw)
In-Reply-To: <4ny8ypfg7u.fsf@holmes.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 23 Jul 2003 10:52:21 -0400")

Ted Zlatanov <tzz@lifelogs.com> writes:

> I hope this clarifies the process.

How should ham in a spam group be handled?  AFAICT, the
ham-exit stuff only runs in a ham group.

The common tasks that I have to do are:

 - unregister a message as spam if I didn't catch it was a false
   positive on the first exit from a spam group

  ( doing this manually via )

    C-x h M-| bogofilter -S  C-x h M-| bogofilter -n

 - register a message as non-spam if I catch it the first time

    C-x h M-| bogofilter -n

   instead of not registering it at all

I may very well be missing something obvious. M-d handles the spam in
the ham group very well although I'm not positive it does the
unregister step.
-- 
Chris Green <cmg@sourcefire.com>
 "Not everyone holds these truths to be self-evident, so we've worked
                  up a proof of them as Appendix A." --  Paul Prescod



  reply	other threads:[~2003-07-23 15:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 16:09 Jody Klymak
2003-07-22 15:26 ` Ted Zlatanov
2003-07-22 16:03   ` Jody Klymak
2003-07-23 20:10     ` Ted Zlatanov
2003-07-23 21:09       ` Jody Klymak
2003-07-23 21:28       ` Jody Klymak
2003-07-24 15:00         ` Ted Zlatanov
2003-07-24 16:50           ` Jody Klymak
2003-07-25  6:47           ` Stefan Reichör
2003-07-25 19:13             ` Ted Zlatanov
2003-07-22 17:24   ` Danny Siu
2003-07-22 21:05     ` David Z Maze
2003-07-23 14:52     ` Ted Zlatanov
2003-07-23 15:38       ` Chris Green [this message]
2003-07-23 19:43         ` Ted Zlatanov

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=m33cgxgsnq.fsf@radon.sfeng.sourcefire.com \
    --to=cmg@sourcefire.com \
    /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).