Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: nnimap: Checking mailbox foo
Date: Tue, 28 Aug 2001 10:54:43 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0108281051550.26321-100000@lie.extundo.com> (raw)
In-Reply-To: <vafae0k38b3.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

On Tue, 28 Aug 2001, Kai Großjohann wrote:

> > It might be possible to collect this information in the background.
> > Or altering the way Gnus looks for unread mail to make things faster.
>
> This sounds as if the IMAP protocol could deliver useful information
> faster, but Gnus doesn't know what to do with it.

Yup.

> What could be the data that IMAP can deliver faster?

Most things except highest and lowest article number in the group:

      MESSAGES       The number of messages in the mailbox.

      RECENT         The number of messages with the \Recent flag set.

      UIDNEXT        The next UID value that will be assigned to a new
                     message in the mailbox.  It is guaranteed that this
                     value will not change unless new messages are added
                     to the mailbox; and that it will change when new
                     messages are added even if those new messages are
                     subsequently expunged.

      UIDVALIDITY    The unique identifier validity value of the
                     mailbox.

      UNSEEN         The number of messages which do not have the \Seen
                     flag set.




  reply	other threads:[~2001-08-28  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 20:31 Kai Großjohann
2001-08-27 20:43 ` Simon Josefsson
2001-08-28  8:20   ` Kai Großjohann
2001-08-28  8:54     ` Simon Josefsson [this message]
2001-08-28  9:56       ` Kai Großjohann
2001-08-27 22:17 ` Joe Casadonte
2001-08-28  0:49   ` Amos Gouaux
2001-08-28  8:19   ` 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=Pine.LNX.4.33.0108281051550.26321-100000@lie.extundo.com \
    --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).