From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el buglets.
Date: Mon, 27 Jan 2003 13:05:03 -0500 [thread overview]
Message-ID: <4nadhmcvu8.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m3ptqi4zq8.fsf@c18072.rivrw2.nsw.optusnet.com.au> (Malcolm Purvis's message of "Mon, 27 Jan 2003 22:08:15 +1100")
On Mon, 27 Jan 2003, malcolmpurvis@optushome.com.au wrote:
> 1) gnus.texi still refers to the spam mark as 'H' instead of '$'.
Fixed, thanks.
> 2) In ham groups it looks like read messages are still sent to ham
> filter for processing even if the group is exited with 'Q'
> (gnus-summary-exit-no-update). Is this the intended behaviour?
> My expectation is that no such processing should occur.
Hmm, this sounds like a bug, but how would I know that no-update was
requested? That function doesn't seem to set any variables to let
summary exit hooks know it was a no-update situation.
> 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. Wouldn't a more generic symbol (ie
> gnus-group-exit-processor-bogofilter) be less confusing and the
> appropriate type of exit processing determined from the group's
> spam/ham classification?
Spam processors make sense for any group (including ham groups), so we
need to distinguish between spam and ham processors.
Ted
next prev parent reply other threads:[~2003-01-27 18:05 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 [this message]
2003-02-02 3:37 ` Malcolm Purvis
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=4nadhmcvu8.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).