From: Niklas Morberg <niklas.morberg@axis.com>
Subject: Re: Ham messages not being moved anymore
Date: Wed, 30 Apr 2003 10:53:13 +0200 [thread overview]
Message-ID: <uel3kl62u.fsf@axis.com> (raw)
In-Reply-To: <4nel3lqhsg.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Tue, 29 Apr 2003 14:29:03 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> It's definitely working here.
Thanks. Now I know more.
The first thing that got me was that messages are no longer
marked as read just by viewing them. This is good and just
something that I needed to learn.
The second thing was that I had configured the parameter
(ham-marks
(gnus-read-mark))
for my spam group. When removing this configuration, read
messages (explicitly marked as read by pressing `d' in the
summary buffer) were moved properly.
With this configuration, read messages are not moved. Am I
using the ham-marks parameter in the wrong way?
All parameters of my spam group included in case there is
something else that might be causing problems:
((uidvalidity . "53242")
(total-expire . t)
(spam-contents gnus-group-spam-classification-spam)
(spam-process
(gnus-group-spam-exit-processor-stat))
(ham-process-destination . "incoming")
(ham-marks
(gnus-read-mark))
(expiry-wait . 4)
(expiry-target . delete))
Niklas
next prev parent reply other threads:[~2003-04-30 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 7:58 Niklas Morberg
2003-04-29 18:29 ` Ted Zlatanov
2003-04-30 8:53 ` Niklas Morberg [this message]
2003-04-30 15:46 ` Ted Zlatanov
2003-05-06 13:18 ` [PATCH] spam.el docstring fix (was: Ham messages not being moved anymore) Niklas Morberg
2003-05-08 13:35 ` [PATCH] spam.el docstring fix 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=uel3kl62u.fsf@axis.com \
--to=niklas.morberg@axis.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).