Gnus development mailing list
 help / color / mirror / Atom feed
From: David Hanak <dhanak-9Zn/qaPSiLf0Rh6LxjfsapVzexx5G7lz@public.gmane.org>
Subject: Repeated spam registration
Date: Wed, 13 Oct 2004 13:34:11 -0500	[thread overview]
Message-ID: <u3c0i4gd8.fsf@isis.vanderbilt.edu> (raw)

Hi,

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?

Thanks,

-- 
David Hanak - Research Engineer
Institute for Software Integrated Systems  |  http://www.isis.vanderbilt.edu
Vanderbilt University                      |      Work phone: (615) 343 1319
Box 1829, Station B, Nashville, TN 37235   |            PGP key ID: 266BC45F




             reply	other threads:[~2004-10-13 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 18:34 David Hanak [this message]
2004-10-14 17:45 ` Xavier Maillard
2004-10-14 18:45   ` Ted Zlatanov
2004-10-14 18:47 ` 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=u3c0i4gd8.fsf@isis.vanderbilt.edu \
    --to=dhanak-9zn/qapsilf0rh6lxjfsapvzexx5g7lz@public.gmane.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).