Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Getting started with spam filtering
Date: Fri, 10 Jan 2003 07:50:29 -0500	[thread overview]
Message-ID: <m3y95tgodm.fsf@heechee.beld.net> (raw)
In-Reply-To: <u65sxqne4.fsf@axis.com> (Niklas Morberg's message of "Fri, 10 Jan 2003 12:01:39 +0100")

On Fri, 10 Jan 2003, niklas.morberg@axis.com wrote:
> Nothing weird to report, but I am a bit confused regarding
> the group parameters for a ham group:
> 
> 1. I set the spam-contents parameter to
>    `gnus-group-spam-classification-ham'
> 
> The parameter documentation says:
> 
>     On summary exit, the specified ham processors will be invoked on
>     ham-marked messages.  Exercise caution, since the ham processor
>     will see the same message more than once because there is no ham
>     message registry.
> 
> 2. I set spam-process to
>    `gnus-group-ham-exit-processor-stat'.
> 
> The thing I don't understand is why I have to do both?
> Wouldn't it be enough to only do (2)?

A ham group does more than just invoke ham processors - you could have
a ham group just because you want to use the spam-process-destination
parameter, and perhaps future functionality.

> What happens if I only do (1) and not (2)?

Nothing harmful.  You are saying "I have a group with articles that
are positively not spam.  I don't want them processed, though."  The
manual has, I think, a good explanation of all the things that apply
for a ham group - if it doesn't, let me know so I can improve it.

Ted




  reply	other threads:[~2003-01-10 12:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 13:51 Niklas Morberg
2003-01-07 14:44 ` Ted Zlatanov
2003-01-07 16:43   ` Frank Schmitt
2003-01-07 17:30     ` Ifile vs. bogofilter (was: Getting started with spam filtering) Frank Schmitt
2003-01-08  6:04   ` Getting started with spam filtering Kai Großjohann
2003-01-08  9:18     ` Lars Magne Ingebrigtsen
2003-01-08 15:26     ` Ted Zlatanov
2003-01-08 23:36       ` Alex Schroeder
2003-01-09 14:23         ` Jorge Godoy
2003-01-09 15:11           ` Andreas Fuchs
2003-01-09 18:38           ` Alex Schroeder
2003-01-10  7:44             ` Niklas Morberg
2003-01-10 12:12               ` Alex Schroeder
2003-01-10 12:51                 ` Niklas Morberg
2003-01-10 13:10                   ` Ted Zlatanov
2003-01-10 13:43                     ` Niklas Morberg
2003-01-10 16:39                       ` Ted Zlatanov
2003-01-24 13:45                         ` Displaying spam score (Was: Re: Getting started with spam filtering) Niklas Morberg
2003-01-10 14:44                   ` Getting started with spam filtering Alex Schroeder
2003-01-15  1:32                   ` Danny Siu
2003-01-10 13:43                 ` Kai Großjohann
2003-01-11 15:41                   ` Simon Josefsson
2003-01-09  8:03       ` Niklas Morberg
2003-01-09 16:24         ` Ted Zlatanov
2003-01-09 23:23           ` Alex Schroeder
2003-01-10  2:07             ` Ted Zlatanov
2003-01-10  4:55               ` Alex Schroeder
2003-01-10  5:54                 ` Ted Zlatanov
2003-01-10 10:41                   ` Niklas Morberg
2003-01-10 11:01                     ` Niklas Morberg
2003-01-10 12:50                       ` Ted Zlatanov [this message]
2003-01-08 11:28   ` Niklas Morberg
2003-01-08 15:23     ` 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=m3y95tgodm.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).