From: Ted Zlatanov <tzz@lifelogs.com>
To: Jan Hoffmann <hoffmann@ifi.lmu.de>
Cc: ding@gnus.org
Subject: Re: Spam.el, ham-marks
Date: Wed, 28 Feb 2007 14:55:38 -0500 [thread overview]
Message-ID: <g69y7mi9hvp.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: <m27iu6sfm8.fsf@jan-mac.wan> (Jan Hoffmann's message of "Sun\, 25 Feb 2007 02\:20\:31 -0800")
On Sun, 25 Feb 2007 02:20:31 -0800 Jan Hoffmann <"hoffmann atcipifilmude"@ifi.lmu.de> wrote:
JH> I'm very used to to tick important incoming articles with the
JH> ticked-mark to remember to answer them.
JH> Now I have started to use spam.el and I like to tread the ticked-mark
JH> as a ham-mark (just as the read-mark).
JH> But when I put (ham-marks (gnus-ticked-mark)) into the
JH> group-parameters of a Group the following problem occurs:
JH> Every time I quit the group, all *old* ticked articles are registered
JH> at bogofilter again (but they should only the first time!).
JH> I have (setq spam-log-to-registry t) set in my .gnus file and the
JH> problem occurs only for the ticked-mark, i.e. if I set for example
JH> (ham-marks (gnus-read-mark)) everything works fine.
JH> Is that a bug?
Hi Jan,
this may be obvious, but did you also load and enable the
gnus-registry?
What version of Gnus do you use?
I'll debug this with you. You're right, the expected behavior is that
old articles should not be registered twice.
Ted
p.s. the e-mail address "hoffmann *"@ifi.lmu.edu wasn't parsed right
by Message-mode, I think. I got an error from SMTP but the address
was already split on space.
next prev parent reply other threads:[~2007-02-28 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 10:20 Jan Hoffmann
2007-02-28 19:55 ` Ted Zlatanov [this message]
2007-02-28 20:14 ` Ted Zlatanov
2007-02-28 23:45 ` Jan Hoffmann
2007-03-02 19:17 ` 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=g69y7mi9hvp.fsf@dhcp-65-162.kendall.corp.akamai.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=hoffmann@ifi.lmu.de \
/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).