Gnus development mailing list
 help / color / mirror / Atom feed
From: Niklas Morberg <niklas.morberg@axis.com>
Subject: Re: spam.el not moving ham message from spam group
Date: Mon, 27 Jan 2003 09:35:03 +0100	[thread overview]
Message-ID: <uvg0bt2h4.fsf@axis.com> (raw)
In-Reply-To: <4nadhq1mzq.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 24 Jan 2003 12:22:33 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 24 Jan 2003, niklas.morberg@axis.com wrote:
>> 
>> However, the ham message is not moved from the spam group.

[snip]

> Try explicitly marking the message as read with the `d'
> command, does it get moved now?

No, it stays put.

It's very easy to reproduce:

Move any ham message to the spam group
Go to the spam group, mark the message as read
Exit spam group
Ham message has not been moved.

Niklas




  parent reply	other threads:[~2003-01-27  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 13:36 Niklas Morberg
2003-01-24 17:22 ` Ted Zlatanov
2003-01-24 19:31   ` David Z Maze
2003-01-27  8:35   ` Niklas Morberg [this message]
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=uvg0bt2h4.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).