Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam/ham exit processors
Date: Mon, 03 Nov 2003 13:41:26 -0500	[thread overview]
Message-ID: <4nllqx47mx.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76ekwpy35x.fsf@newjersey.ppllc.com> (Jake Colman's message of "Mon, 03 Nov 2003 08:47:38 -0500")

On Mon, 03 Nov 2003, colman@ppllc.com wrote:

>>From my reading of the manual, it seems that the suggested or
>>anticipated
> modus operandi is to move spam in a ham-classified group to a
> spam-classified group for furthur processing and to move ham from a
> spam-classified group over to a ham-classified group for furthur
> processing.  

Nope, you can process the spam at the point of origin or in a central
group.  Most people like a central "spam" group better.

> In such aa situation, do you need both types of exit processors in
> both types of groups?  Or do you just need a ham exit processors for
> the ham-classified group and a spam exit processor for the
> spam-classified group?  

You can do it either way, and it is just a different approach to the
same problem.

> I'm assuming that having an exit processor when you don't need one
> costs you a bit in performance.

The only performance cost is for the analysis of spam or ham, if
there's nothing to be done you won't pay any penalties in performance
at all.  So you can choose to batch up the processing in one group or
break it up over several groups.  It depends on your system, the
particular spam/ham processor's speed, the size of the messages...

Ted



  reply	other threads:[~2003-11-03 18:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 13:47 Jake Colman
2003-11-03 18:41 ` Ted Zlatanov [this message]
2003-11-03 20:29   ` Kai Grossjohann
2003-11-03 20:31     ` Russ Allbery
2003-11-03 21:26       ` Ted Zlatanov
2003-11-03 21:43         ` Russ Allbery
2003-11-04  2:28           ` Ted Zlatanov
2003-11-04  3:03             ` Russ Allbery
2003-11-04 15:11             ` Jake Colman
2003-11-04 16:17               ` Ted Zlatanov
2003-11-04 17:37                 ` Jake Colman
2003-11-04 22:31                   ` Kai Grossjohann
2003-11-03 21:25     ` Ted Zlatanov
2003-11-03 22:10       ` Kai Grossjohann
2003-11-04  2:20         ` Ted Zlatanov
2003-11-04 15:08       ` Jake Colman

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=4nllqx47mx.fsf@lockgroove.bwh.harvard.edu \
    --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).