Gnus development mailing list
 help / color / mirror / Atom feed
From: Niklas Morberg <niklas.morberg@axis.com>
Subject: The agent shows ghost messages (was: spam-stat broken?)
Date: Wed, 12 Feb 2003 16:00:46 +0100	[thread overview]
Message-ID: <un0l1k0gx.fsf_-_@axis.com> (raw)
In-Reply-To: <4nadh1k3wy.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 12 Feb 2003 08:46:21 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Wed, 12 Feb 2003, niklas.morberg@axis.com wrote:
>> 
>> The move routines seem to be working better now, but after
>> some more testing I still see the problem with non-existing
>> messages being displayed in the summary buffer by the agent.
>
> Can you check now? If there is still a problem, something
> is wrong in the interaction between the agent and
> gnus-summary-move-article.

There is a problem, but it has nothing to do with the spam
functionality. I'm pretty sure the problem is with the agent.

Here's a way to repeat it:

1. Start with two unread and undownloaded messages in a
   group.

2. Read the first message.

3. Move the second message to another group with `B m'
   without reading it.

4. Exit the group.

5. Re-enter the same group. The second message shows up in
   the summary buffer, but it not possible to look at it.
   It has not been downloaded and it is not on the server.

This only happens if gnus-agent-mark-unread-after-downloaded
is nil. Setting g-a-m-u-a-d to non-nil makes the problem go
away.

I saw this a lot because I used the spam functionality to do
step 3 above and assumed that that was the culprit.

Thanks for the other fixes in spam.el, though -- they were
certainly not made in vain. I find the spam functionality
much more stable now.

Niklas




  reply	other threads:[~2003-02-12 15:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05  4:15 spam-check-BBDB bug?/bbdb whitelist split function Bill White
2003-02-05 14:47 ` Ted Zlatanov
2003-02-05 14:59   ` Bill White
2003-02-05 17:57     ` Ted Zlatanov
2003-02-05 15:07   ` Niklas Morberg
2003-02-05 17:51     ` Ted Zlatanov
2003-02-10  8:13       ` spam-stat broken? (was: spam-check-BBDB bug?/bbdb whitelist split function) Niklas Morberg
2003-02-11  8:15         ` spam-stat broken? Niklas Morberg
2003-02-11 17:56           ` Ted Zlatanov
2003-02-11 20:28             ` Ted Zlatanov
2003-02-12  9:49               ` Niklas Morberg
2003-02-12 11:16                 ` Ted Zlatanov
2003-02-12 13:44                   ` Ted Zlatanov
2003-02-12 13:46                 ` Ted Zlatanov
2003-02-12 15:00                   ` Niklas Morberg [this message]
2003-02-12 15:48                     ` The agent shows ghost messages Ted Zlatanov
2003-02-12 16:29                     ` The agent shows ghost messages (was: spam-stat broken?) Kevin Greiner
2003-02-13  7:53                       ` The agent shows ghost messages Niklas Morberg
2003-02-13  8:44                       ` The agent shows ghost messages (was: spam-stat broken?) Niklas Morberg
2003-02-13 13:50                         ` The agent shows ghost messages Kevin Greiner
2003-02-13 14:50                           ` Niklas Morberg

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=un0l1k0gx.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).