From: Niklas Morberg <niklas.morberg@axis.com>
Subject: spam.el not moving ham message from spam group
Date: Fri, 24 Jan 2003 14:36:09 +0100 [thread overview]
Message-ID: <u1y32zn3q.fsf@axis.com> (raw)
Entering a spam group, reading a ham message (thus making it
ham), and then leaving the spam group generates the
following messages:
Retrieving newsgroup: spam...
nnimap: Updating info for spam...done
Fetching headers for spam...done
Generating summary...done
Marking unread articles as spam
No more unread articles
call-interactively:
End of buffer
No more unread articles
No more articles
Exiting summary buffer and applying spam rules
Registering spam with spam-stat
Wrote c:/cygwin/home/niklas/.spam-stat.el
Moving ham messages from spam group
However, the ham message is not moved from the spam group.
My settings for the spam group are:
((uidvalidity . "53242")
(total-expire . t)
(spam-contents gnus-group-spam-classification-spam)
(spam-process
(gnus-group-spam-exit-processor-stat))
(ham-process-destination . "incoming")
(expiry-wait . 4))
Is anyone else seeing this?
Niklas
next reply other threads:[~2003-01-24 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 13:36 Niklas Morberg [this message]
2003-01-24 17:22 ` Ted Zlatanov
2003-01-24 19:31 ` David Z Maze
2003-01-27 8:35 ` Niklas Morberg
2003-01-27 19:11 ` Torsten Hilbrich
2003-01-27 19:37 ` 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=u1y32zn3q.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).