Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Wed, 11 Aug 2004 21:11:34 -0500	[thread overview]
Message-ID: <un01114x5.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <871xidtl04.fsf@mail.contactor.se>

Mats Lidell <matsl@contactor.se> writes:

> I read my mail daily with squirrelmail as well as with gnus. I have
> noticed that mail I read with squirrelmail isn't always possible to
> see in gnus. (I haven't check if the problem always is there. Some
> mails might show up in both.) I have however found a workaround. If I
> delete the .agentview and .overview files the summary is initialized
> correctly and the mail read by squirrelmail is seen in gnus as well.
>
> There is however no way that this situation can be known from gnus. If
> it wasn't that I remember having seen those mails I wouldn't have
> missed them. So I feel that the situation is bad. nnimap shouldn't
> behave like this. Why isn't the overview-file updated when the
> contents in the imap folder is changed from outside of gnus?
>
> I have reported this before but haven't gotten any good response saying
> either that my setup is broken or that nnimap is broken. Am I the only
> one seeing this?

The problem is that, when the agent is turned on, your backend
requests don't go directly to the backend.  They instead go to the
agent which tries to respond using what it has locally cached.  If,
and only if, you request something that is not in the cache, will the
agent request the MISSING content from the real backend.

Frankly, I don't see how to make the agent work better with nnimap
without introducing nnimap specific code into the agent or changing
the backend interface.  Neither is something to take lightly so I
don't believe that this situation will be changing anytime soon.

One possibility, have you set gnus-agent-consider-all-articles to t?
If you do so, the agent will let gnus download read messages.  That
may fix part of your problem.

If that doesn't help, then I'd suggest that you either 1) turn off the
agent, or 2) periodically delete the .agentview file.  You shouldn't
need to delete the .overview file.

Kevin





  parent reply	other threads:[~2004-08-12  2:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner [this message]
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris
2004-08-16 19:54         ` Steven E. Harris
2004-08-17 11:39         ` Steinar Bang

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=un01114x5.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).