From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam-stat broken?
Date: Wed, 12 Feb 2003 08:44:24 -0500 [thread overview]
Message-ID: <4nd6lxk407.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <4n4r79px4y.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 12 Feb 2003 06:16:13 -0500")
On Wed, 12 Feb 2003, tzz@lifelogs.com wrote:
> As I said, I'm not sure it's the right way. Another issue is, what
> if you have articles process-marked before you exit a group? Will
> the process-mark get removed before the spam.el routines get
> invoked? I didn't test this yesterday because I was in a hurry.
Both issues fixed:
- previously process-marked articles are unmarked now before spam/ham
articles of interest are process-marked
- gnus-summary-move-article is called just once
Thanks
Ted
next prev parent reply other threads:[~2003-02-12 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 4:15 spam-check-BBDB bug?/bbdb whitelist split function Bill White
2003-02-05 14:47 ` Ted Zlatanov
2003-02-05 14:59 ` Bill White
2003-02-05 17:57 ` Ted Zlatanov
2003-02-05 15:07 ` Niklas Morberg
2003-02-05 17:51 ` Ted Zlatanov
2003-02-10 8:13 ` spam-stat broken? (was: spam-check-BBDB bug?/bbdb whitelist split function) Niklas Morberg
2003-02-11 8:15 ` spam-stat broken? Niklas Morberg
2003-02-11 17:56 ` Ted Zlatanov
2003-02-11 20:28 ` Ted Zlatanov
2003-02-12 9:49 ` Niklas Morberg
2003-02-12 11:16 ` Ted Zlatanov
2003-02-12 13:44 ` Ted Zlatanov [this message]
2003-02-12 13:46 ` Ted Zlatanov
2003-02-12 15:00 ` The agent shows ghost messages (was: spam-stat broken?) Niklas Morberg
2003-02-12 15:48 ` The agent shows ghost messages Ted Zlatanov
2003-02-12 16:29 ` The agent shows ghost messages (was: spam-stat broken?) Kevin Greiner
2003-02-13 7:53 ` The agent shows ghost messages Niklas Morberg
2003-02-13 8:44 ` The agent shows ghost messages (was: spam-stat broken?) Niklas Morberg
2003-02-13 13:50 ` The agent shows ghost messages Kevin Greiner
2003-02-13 14:50 ` Niklas Morberg
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=4nd6lxk407.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).