From: Malcolm Purvis <malcolmpurvis@optushome.com.au>
Cc: ding@gnus.org
Subject: Re: spam.el buglets.
Date: Sun, 02 Feb 2003 14:37:49 +1100 [thread overview]
Message-ID: <m3smv7bbea.fsf@c18072.rivrw2.nsw.optusnet.com.au> (raw)
In-Reply-To: <4nadhmcvu8.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 27 Jan 2003 13:05:03 -0500")
>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
Ted> On Mon, 27 Jan 2003, malcolmpurvis@optushome.com.au wrote:
>> 3) I am having difficulty understanding the advantages of having the choice
>> of both spam and ham exit processors (ie
>> gnus-group-spam-exit-processor-bogofilter and
>> gnus-group-ham-exit-processor-bogofilter) for a given group when only one
>> will apply.
Ted> Spam processors make sense for any group (including ham groups), so we
Ted> need to distinguish between spam and ham processors.
I can see the value in having different groups (even the same group) processed
with different spam processors, but not the ability for a given processor to
handle a group's ham but not spam. ie, why would I want bogofilter to progress
a group's ham but not spam. Surely a more general 'feed everything in this
group to bogofilter (and/or whatever) would be easier to understand.
BTW, this is what happened to me. For a week or so I all of my spam being sent
to bogofilter, but none of the ham, and I was wondering what was going on!
Malcolm
--
Malcolm Purvis <malcolmpurvis@optushome.com.au>
The hidden, terrible cost of nuclear warfare is Really Bad Public Art.
- Angus McIntyre, alt.peeves, 13/3/02.
next prev parent reply other threads:[~2003-02-02 3:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 11:08 Malcolm Purvis
2003-01-27 18:05 ` Ted Zlatanov
2003-02-02 3:37 ` Malcolm Purvis [this message]
2003-02-02 4:50 ` 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=m3smv7bbea.fsf@c18072.rivrw2.nsw.optusnet.com.au \
--to=malcolmpurvis@optushome.com.au \
--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).