From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Mailbox foo modified -- for all groups?
Date: Tue, 25 Feb 2003 14:26:28 +0100 [thread overview]
Message-ID: <iluy9445w57.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84fzqc3ifc.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Tue, 25 Feb 2003 08:53:27 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> When I say `g', it tells me `Mailbox foo modified' for many different
> groups foo, including many that haven't changed in a year or so. A
> subsequent `J s' then fetches headers for all those groups (it
> seems), which takes quite a while.
>
> How come Gnus thinks these groups are modified, and is there a way to
> tell it they aren't, and can the agent skip trying to fetch headers
> for them?
Did you frob nnimap-retrieve-groups-asynchronous? The code works by
comparing UIDVALIDITY and UIDNEXT, and if any of those has changed,
the message is printed. Perhaps edebugging nnimap-retrieve-groups
helps?
next prev parent reply other threads:[~2003-02-25 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 7:53 Kai Großjohann
2003-02-25 13:26 ` Simon Josefsson [this message]
2003-02-28 13:09 ` 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=iluy9445w57.fsf@latte.josefsson.org \
--to=jas@extundo.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).