From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Repeated spam registration
Date: 14 Oct 2004 14:47:21 -0400 [thread overview]
Message-ID: <4n1xg1gmrq.fsf@lifelogs.com> (raw)
In-Reply-To: <u3c0i4gd8.fsf@isis.vanderbilt.edu> (David Hanak's message of "Wed, 13 Oct 2004 13:34:11 -0500")
On Wed, 13 Oct 2004, dhanak@isis.vanderbilt.edu wrote:
> I use spam.el with bogofilter to filter spam with great satisfaction.
> There is one minor detail, though which is bothering me. Every once in
> a while I have to go back to old, read mail and read it again. These
> messages are ususally already marked as ham. After I reread them and
> exit the group, they are obviously marked as read, which is a ham mark,
> so they are *reregistered* with bogofilter. Because I use the registry
> to remember spam classification, they are duly unregistered before the
> reregistration. So this is what I get in the *Messages* buffer:
>
> ,----[ *Messages* ]
>| Unregistering 1 specific articles as ham using backend spam-use-bogofilter
>| Registering 1 articles as ham using backend spam-use-bogofilter
>| 1 ham messages were processed by backend spam-use-bogofilter.
> `----
>
> This is of course slow and completely unnecessary. I tried adding the
> ancient-mark to the list of ham-marks, but that only resulted in the
> omission of the unregistration, the reregistration was still done, which
> is obviously worse. Is this how it is supposed to work? Is there a way
> to solve this problem?
I noticed this problem too, I'll see what's going on. In the
meantime, rest easy knowing that your CPU is not underutilized :)
Ted
prev parent reply other threads:[~2004-10-14 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 18:34 David Hanak
2004-10-14 17:45 ` Xavier Maillard
2004-10-14 18:45 ` Ted Zlatanov
2004-10-14 18:47 ` Ted Zlatanov [this message]
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=4n1xg1gmrq.fsf@lifelogs.com \
--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).