Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: spam/ham exit processors
Date: Mon, 03 Nov 2003 20:29:05 +0000	[thread overview]
Message-ID: <87ptg9ryb2.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <4nllqx47mx.fsf@lockgroove.bwh.harvard.edu>

Ted Zlatanov <tzz@lifelogs.com> writes:

> 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.

Oh!  Does this mean that people could set
gnus-spam-process-destinations to nnml:spam, say, then set the
spam-process parameter just on nnml:spam, for it to be added to the
blacklist or whatever?  (Whereas spam-process remains unset/nil in all
other groups except nnml:spam?)

Fascinating.






  reply	other threads:[~2003-11-03 20:29 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
2003-11-03 20:29   ` Kai Grossjohann [this message]
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=87ptg9ryb2.fsf@emptyhost.emptydomain.de \
    --to=kai@emptydomain.de \
    /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).