Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Expiry problems...
Date: Thu, 25 Nov 1999 09:48:18 -0800	[thread overview]
Message-ID: <19991125094818.A1402@satellite.local.lan> (raw)
In-Reply-To: =?iso-8859-1?Q?=3Cvafr9hefrks=2Efsf=40lucy=2Ecs=2Euni-dortmund=2Ede=3E?= =?iso-8859-1?Q?=3B_from_Kai_Gro=DFjohann_on_Thu=2C_Nov_25=2C_1999_at_05:?= =?iso-8859-1?Q?45:23PM_+0100?=

On Thu, Nov 25, 1999 at 05:45:23PM +0100, Kai Großjohann wrote:
> John S Cooper <John.Cooper@citrix.com> writes:
> 
> > However, since switching to nnimap, I now notice that many articles
> > which should have been expired (marked E and older than 7 days) are
> > now displayed with the ancient "O" mark when I enter the group with
> > a prefix argument.
> 
> What happens when you try to view them?  If that produces an error and
> the article isn't there, then you have hit the overview cache problem:
> nnimap caches overview entries on the local disk, but the cache isn't
> cleaned of old entries.
> 
> Every once in a while, you could delete the overview cache.

I know this isn't the ding list (I set replies to ding) but it was too
close to something similar with the way gnus-agent handles messages
under agent-unplugged when the message is not downloaded. The summary
info is there and present in .overview, but no actual file exists. Is
this cached somewhere too?

Can that be deleted somehow too?  And what or where is the "overview
cache"?


       reply	other threads:[~1999-11-25 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uyabm1y1y.fsf@KONTIKI.citrix.com>
     [not found] ` <vafr9hefrks.fsf@lucy.cs.uni-dortmund.de>
1999-11-25 17:48   ` Harry Putnam [this message]
1999-11-25 18:14     ` Kai Großjohann

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=19991125094818.A1402@satellite.local.lan \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    /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).