Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Performance problem of imap move
Date: Wed, 28 Jan 2015 11:45:00 +1100	[thread overview]
Message-ID: <87r3uf20oj.fsf@building.gnus.org> (raw)
In-Reply-To: <874mrcps1a.fsf@gnu.org> (Tassilo Horn's message of "Tue, 27 Jan 2015 09:05:37 +0100")

Tassilo Horn <tsdh@gnu.org> writes:

>>> 18:26:59 [hermes.netfonds.no] 2741 SELECT "Test".
>>> 18:27:00 [hermes.netfonds.no] 2742 APPEND "Test" {422}.
>>> 18:27:00 [hermes.netfonds.no] 2743 EXAMINE "Test" (QRESYNC (1286911992 20)).

[...]

> 09:01:32 [mail.messagingengine.com] 1429 SELECT "INBOX.Sent Items"
> 09:01:32 [mail.messagingengine.com] 1430 APPEND "INBOX.Sent Items" {1953}
> 09:01:32 [mail.messagingengine.com] 1431 EXAMINE "INBOX.Sent Items" (QRESYNC (1103381936 206930))

So that's basically the same as what happens in my group...

> 09:01:32 [mail.messagingengine.com] 1432 SELECT "INBOX.Sent Items"
> 09:01:32 [mail.messagingengine.com] 1433 UID STORE 1:2385 +FLAGS.SILENT (\Seen)

But that's odd.  It's marking articles 1 to 2385 as seen?  I would have
expected it to mark at most one article...

> And now after exiting the summary, my group line shows
>
>   19739: nnimap+Fastmail:INBOX.mailinglists.ding
>
> where 2 or 3 is actually the right unread count.  And this time, `g' or
> `M-g' don't fix the unread count anymore.

That is even weirder.  `M-g' is supposed to do a complete rescan, making
Gnus reflect the state of the messages on the IMAP server totally.

This is very odd.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2015-01-28  0:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:06 Mickaël Rémond
2015-01-21 14:11 ` Mickaël Rémond
2015-01-25  4:57   ` Lars Ingebrigtsen
2015-01-26  2:52     ` Lars Ingebrigtsen
2015-01-26 12:11       ` Tassilo Horn
2015-01-26 16:55         ` Steinar Bang
2015-01-27  0:54         ` Lars Ingebrigtsen
2015-01-27  7:23           ` Tassilo Horn
2015-01-27  7:28             ` Tassilo Horn
2015-01-27  7:30             ` Lars Ingebrigtsen
2015-01-27  8:01               ` Tassilo Horn
2015-01-27  8:05                 ` Tassilo Horn
2015-01-28  0:45                   ` Lars Ingebrigtsen [this message]
2015-01-27  3:46         ` Eric Abrahamsen
2015-01-27  4:48           ` Lars Ingebrigtsen
2015-01-27  5:02             ` Eric Abrahamsen
2015-01-27  5:09               ` Lars Ingebrigtsen
2015-01-27 14:41                 ` Steinar Bang
2015-01-28  2:06                   ` Dave Goldberg
2015-01-29  5:11                     ` Dave Goldberg
2015-01-28  2:29                 ` Eric Abrahamsen
2015-01-28  4:08                   ` Eric Abrahamsen
2015-01-28  4:10                     ` Eric Abrahamsen
2015-01-28  4:32                       ` Eric Abrahamsen
2015-01-28  5:08                         ` Lars Ingebrigtsen
2015-01-28  5:13                           ` Lars Ingebrigtsen
2015-01-28  5:52                             ` Eric Abrahamsen
2015-01-28 14:22                             ` Tassilo Horn
2015-01-29  1:08                               ` Lars Ingebrigtsen

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=87r3uf20oj.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --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).