From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Ham messages not being moved anymore
Date: Tue, 29 Apr 2003 14:29:03 -0400 [thread overview]
Message-ID: <4nel3lqhsg.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <usms1ybst.fsf@axis.com> (Niklas Morberg's message of "Tue, 29 Apr 2003 09:58:58 +0200")
On Tue, 29 Apr 2003, niklas.morberg@axis.com wrote:
> When I read ham messages in my spam group they will no
> longer be moved out of the spam group when exiting.
>
> It has worked before and I have made no changes to my
> configuration.
>
> Trying different settings for local ham-marks did not help.
It's definitely working here. Run
M-: (spam-ham-move-routine (gnus-parameter-ham-process-destination gnus-newsgroup-name))
while in the summary buffer. Put (debug) statements in
spam-ham-move-routine to see what's going wrong, if it does.
Ted
next prev parent reply other threads:[~2003-04-29 18:29 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 [this message]
2003-04-30 8:53 ` Niklas Morberg
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=4nel3lqhsg.fsf@lockgroove.bwh.harvard.edu \
--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).