From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/81670 Path: news.gmane.org!not-for-mail From: Matt Ford Newsgroups: gmane.emacs.gnus.general Subject: 4266 is the 666 of the IMAP world (retrieval issues and odd behaviours) Date: Tue, 03 Apr 2012 17:55:53 +0100 Organization: Dancingfrog Message-ID: <87ehs4ah5y.fsf@dancingfrog.co.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1333473410 9738 80.91.229.3 (3 Apr 2012 17:16:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 3 Apr 2012 17:16:50 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M29949@lists.math.uh.edu Tue Apr 03 19:16:49 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SF7Lb-0003uX-KR for ding-account@gmane.org; Tue, 03 Apr 2012 19:16:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1SF7K8-0003gX-4G; Tue, 03 Apr 2012 12:15:16 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1SF7K6-0003gL-An for ding@lists.math.uh.edu; Tue, 03 Apr 2012 12:15:14 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1SF7K4-0007EB-JT for ding@lists.math.uh.edu; Tue, 03 Apr 2012 12:15:13 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1SF7K2-00010k-I8 for ding@gnus.org; Tue, 03 Apr 2012 19:15:10 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SF7K0-0002gi-Tz for ding@gnus.org; Tue, 03 Apr 2012 19:15:08 +0200 Original-Received: from host-92-22-235-129.as13285.net ([92.22.235.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Apr 2012 19:15:08 +0200 Original-Received: from matt by host-92-22-235-129.as13285.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Apr 2012 19:15:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 51 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: host-92-22-235-129.as13285.net User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux) Cancel-Lock: sha1:w1YfbaGCx5CBTia7ZIMmXvTLCM0= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:81670 Archived-At: Hi, Returned to Gnus after hearing that all IMAP code is spiffy fast again...which it is :-) But I do have some issues... I've checked out the latest (as of a couple of days ago) git development branch and configured Gnus to run against Gmail and my works Exchange 2010 server. Gmail is great! :-D But I don't have so much mail in there. Exchange not so :`( Without the Gnus agent on when fetching my largish Inbox on Exchange I have found that I can happily enter the Inbox file from the group buffer if I request 4265 articles (C-u SPACE 4265 or gnus-group-read-group). If I request 4266 articles then Gnus reports "No unread news" and moves the cursor to the bottom of the buffer. In both cases the total number of available articles is reported correctly. I can get the data though if I jump into the buffer and then run "/ o" or gnus-summary-insert-old-articles. Interestingly this function returns not the number of messages but what looks like the max article UID in the prompt (bug or feature?). Switching on debugging (via nnimap-record-commands t) shows a spectacularly big fetch line for gnus-group-read-group when asking for everything. I'm wondering if the request is too large based on this rather flimsy evidence...to say the UIDs are not contiguous is an understatement. How does this code work? Are requests split into sensible chunks? Interestingly the gnus-summary-insert-old-articles command doesn't log any activity in *imap log* so that's probably a bug in itself but also hints something is going on quite different. I replicated this on two different machines... If you grow your mailbox slowly and use Gnus agent then you don't hit any issues as it kicks in when you request everything... Anyone seen anything similar or have thoughts how I might get around this? Phew! -- Matt