Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Exchange Updating Info Problem
Date: Thu, 03 Apr 2008 12:41:15 -0400	[thread overview]
Message-ID: <76y77udh78.fsf@dev-d01.ppllc.com> (raw)


If I enter an Exchange IMAP group with alot of read messages, Gnus takes
an awfully long time to process.  My imap-log shows the following:

1167 SELECT "INBOX/Principia"
* 15310 EXISTS
* 2 RECENT
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
* OK [UNSEEN 15309] Is the first unseen message
* OK [UIDVALIDITY 1296] UIDVALIDITY value
* OK [UIDNEXT 15320] The next unique identifier value
1167 OK [READ-WRITE] SELECT completed.
1168 UID SEARCH UNSEEN UNDELETED
* SEARCH 15318 15319
1168 OK SEARCH completed.
1169 UID SEARCH SEEN
* SEARCH 1 2 3 4..............

The result if the "SEARCH SEEN" is a huuuuuge amount of data.  It
totally floods my imap-log.

Following this is the following:

1169 OK SEARCH completed.
1170 UID SEARCH FLAGGED
* SEARCH
1170 OK SEARCH completed.
1171 UID SEARCH ANSWERED
* SEARCH 15300
1171 OK SEARCH completed.
1172 UID SEARCH RECENT
* SEARCH 15318 15319
1172 OK SEARCH completed.
1173 EXAMINE "INBOX/Principia"

plus more stuff.

The problem appears to be the SEARCH SEEN command.

Thanks for any help.

...Jake


-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com




             reply	other threads:[~2008-04-03 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 16:41 Jake Colman [this message]
2008-04-08 21:44 ` Ted Zlatanov
2008-04-09  2:28   ` Jake Colman
2008-04-09 16:26   ` Jake Colman
2008-04-09 20:30     ` Ted Zlatanov
2008-04-09 20:35   ` James Cloos
2008-04-10 13:12     ` Ted Zlatanov
2008-04-10 14:51       ` James Cloos
2008-04-10 18:18         ` Jake Colman
2008-04-10 18:55           ` Ted Zlatanov

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=76y77udh78.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.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).