From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Exchange 2007 Issues When Copying Between Folders Date: Tue, 01 Apr 2008 16:06:41 +0200 Message-ID: <878wzxr7ny.fsf@mocca.josefsson.org> References: <767ifjymej.fsf@dev-d01.ppllc.com> <868wzypw22.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1207059032 26665 80.91.229.12 (1 Apr 2008 14:10:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Apr 2008 14:10:32 +0000 (UTC) Cc: Jake Colman , ding@gnus.org, Emacs developers To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 01 16:10:54 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jgh9F-0002FT-L0 for ged-emacs-devel@m.gmane.org; Tue, 01 Apr 2008 16:07:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jgh8d-00031E-H5 for ged-emacs-devel@m.gmane.org; Tue, 01 Apr 2008 10:06:59 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jgh8Z-00030s-Qk for emacs-devel@gnu.org; Tue, 01 Apr 2008 10:06:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jgh8Y-00030c-EN for emacs-devel@gnu.org; Tue, 01 Apr 2008 10:06:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jgh8Y-00030Z-AP for emacs-devel@gnu.org; Tue, 01 Apr 2008 10:06:54 -0400 Original-Received: from yxa.extundo.com ([83.241.177.38]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jgh8X-00032d-AG for emacs-devel@gnu.org; Tue, 01 Apr 2008 10:06:54 -0400 Original-Received: from mocca.josefsson.org (yxa.extundo.com [83.241.177.38]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id m31E6fFN001950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Apr 2008 16:06:42 +0200 OpenPGP: id=B565716F; url=http://josefsson.org/key.txt X-Hashcash: 1:22:080401:emacs-devel@gnu.org::xnqEiCO/mi+L1Foy:3mDb X-Hashcash: 1:22:080401:colman@ppllc.com::YCzJPXFs7OkzYd3b:6M2A X-Hashcash: 1:22:080401:tzz@lifelogs.com::hy0tzCkbbPbEY2zM:86jo X-Hashcash: 1:22:080401:ding@gnus.org::n2afk3MiNu6SPSRt:DUFS In-Reply-To: <868wzypw22.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 31 Mar 2008 13:50:29 -0500") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux) X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com X-Virus-Status: Clean X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:94111 gmane.emacs.gnus.general:66631 Archived-At: Ted Zlatanov writes: > On Mon, 31 Mar 2008 10:54:12 -0400 Jake Colman wrote: > > JC> Ted suggested that I post here as I find more issues with using Gnus > JC> with Exchange 2007. > > JC> If I move an email between IMAP folders ('B m'), I get the following messages: > > JC> Registry: Registering article 6 with group nnimap+exchange-d01:INBOX/Development/gnu > JC> Registry: Registering article 7 with group nnimap+exchange-d01:INBOX/Development/gnu > JC> Moving to nnimap+exchange-d01:INBOX/Development/CVS: (6)... > JC> nnimap-request-move-article: this is an internal move > JC> The specified message set is invalid. > JC> Couldn't Move article 6: The specified message set is invalid. > JC> nnimap: Updating info for nnimap+exchange-d01:INBOX/Development/gnu... > JC> nnimap: Updating info for nnimap+exchange-d01:INBOX/Development/gnu...done > > JC> The message is, in fact, copied between the 'gnu' folder and the 'CVS' > JC> folder but it is not deleted from the 'gnu' folder. > > JC> I am attaching the output of the imap-debug buffer showing everything starting > JC> with pressing 'B m'. > > The command that caused the problem: > > 511 UID FETCH * UID > > (copying emacs-devel regarding the maintenance issue) > > Simon Josefsson hasn't replied to my pings, so I think he may not be > available for imap.el support. Simon, please let us know if that's not > the case. Hi! Sorry for not responding, I have been busy with other things, and I don't have much time to work on (nn)imap.el any more. I have time to review concrete patches, but little time to help debug problems with some servers. However, the recently installed patch for Gnus is definitely the wrong thing: - (imap-fetch "1,*" "UID" nil 'nouidfetch) + (imap-fetch "1:*" "UID" nil 'nouidfetch) This generates thousands and thousands of unnecessary lines of output, such as: 669 FETCH 1:* UID * 1 FETCH (UID 53159) * 2 FETCH (UID 53160) * 3 FETCH (UID 53161) ... * 103915 FETCH (UID 157074) * 103916 FETCH (UID 157075) * 103917 FETCH (UID 157076) 669 OK Completed That's about 2-3MB of output, and that was getting information for one of my folders (I subscribe to maybe 100-150 folders..). This slows down pressing 'g' on my server from sub-seconds to a very long time (I pressed C-g after half a minute). This is how the output should look like: 698 FETCH 1,* UID * 1 FETCH (UID 53159) * 103918 FETCH (UID 157077) 698 OK Completed That's 89 bytes and takes ms's to transfer. If you want this bug workaround in the code, please make it conditional on some variable that is disabled by default. I suggest documenting that this may slow down things considerably. > I'm willing to dig further and maybe support imap.el if no one else > wants it, but honestly the IMAP RFCs are unpleasant and annoy me, so I > need a better explanation of the protocol. Google was not helpful. Can > anyone suggest an IMAP primer I can read? I'm interested in the actual > protocol, so the more concrete the examples, the better. I'm not aware of any, and I would agree that the RFC is unfriendly... if you can't find any primer, just toggle imap-log and try to understand the commands send by Gnus for each operation that is needed. Read the RFC for full explanations of some things. /Simon