Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: nnimap and sticky cache
Date: Wed, 25 Mar 2009 11:48:20 +0100	[thread overview]
Message-ID: <m27i2d98uj.fsf@randomsample.de> (raw)
In-Reply-To: <m2hc1iv11i.fsf@boostpro.com> (David Abrahams's message of "Tue, 24 Mar 2009 21:33:45 -0400")

David Abrahams <dave@boostpro.com> writes:
> on Tue Mar 24 2009, Tassilo Horn <tassilo-AT-member.fsf.org> wrote:
>
>> David Abrahams <dave@boostpro.com> writes:
>>
>> Hi David,
>>
>>> Old articles that have since been deleted through other clients still
>>> show up in the summary (bad) but sometimes "turn black" (show up as
>>> deleted) when I try to read them (also bad).  The latest problem is
>>> that I've added 'Message-ID to gnus-extra-headers, but `/-x
>>> Message-ID<RET>xxxxx' turns up nothing, even though I have a message
>>> containing xxxxx in its Message-ID header.  I've had this sort of
>>> problem for years!
>>
>> Do you use the agent for you imap server?  
>
> Yup.  But even if I turn the agent off I still see this problem.

As Tassilo already said, turn the agent off and delete the agent files
still in ~/News/agent. Next, you could try to set the server variable
nnimap-nov-is-evil for your nnimap server definition and also delete all
overview files for the server (usually
~/News/overview/nnimap/SERVER). (I think all of this is safe to do, but
better keep a backup when deleting stuff from ~/News).

-David



  parent reply	other threads:[~2009-03-25 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 20:32 David Abrahams
2009-03-24 21:04 ` Tassilo Horn
2009-03-25  1:33   ` David Abrahams
2009-03-25  7:46     ` Tassilo Horn
2009-03-25 10:48     ` David Engster [this message]
2009-03-28 19:50       ` David Abrahams
2009-03-29 17:30         ` Tassilo Horn
2009-03-30 20:15           ` gnus-extra-headers and gnus-summary-limit-to-extra (was: nnimap and sticky cache)? David Abrahams
2009-03-31  6:41             ` gnus-extra-headers and gnus-summary-limit-to-extra Tassilo Horn

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=m27i2d98uj.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --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).