From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: ham-mark and expire mark
Date: Tue, 08 Feb 2005 14:15:36 -0500 [thread overview]
Message-ID: <4npszavp5z.fsf@lifelogs.com> (raw)
In-Reply-To: <m38y6bhm8y.fsf@neo.luffy.cx>
On Sun, 30 Jan 2005, vincent.bernat@raysa.org wrote:
> On group with auto expire flag, read messages are not processed as
> ham. I suppose this is due to the fact they are marked as expirable
> instead of read. However, I don't see how to tell to spam.el that
> messages that have the expire mark should be marked as ham.
The options are:
:parameter-type '(list :tag "Ham mark choices"
(set
(variable-item gnus-del-mark)
(variable-item gnus-read-mark)
(variable-item gnus-ticked-mark)
(variable-item gnus-killed-mark)
(variable-item gnus-kill-file-mark)
(variable-item gnus-low-score-mark)))
so I would need to add the expire mark gnus-expirable-mark to the
default set. I'm not sure that's a good idea - I don't use
auto-expire a lot, so any suggestions are welcome.
You can just hit `d' on the messages you want processed as ham, that
will give them the gnus-del-mark. Does that help or do you need a lot
of it to happen?
Ted
prev parent reply other threads:[~2005-02-08 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 23:02 Vincent Bernat
2005-02-08 19:15 ` 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=4npszavp5z.fsf@lifelogs.com \
--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).