From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68234 Path: news.gmane.org!not-for-mail From: Bjorn Solberg Newsgroups: gmane.emacs.gnus.general,gmane.emacs.devel Subject: Re: IMAP and Exchange 2007 - imap-fetch-safe Date: Sun, 01 Feb 2009 07:43:32 -0800 Message-ID: References: <87iqphil5p.fsf@liv.ac.uk> <87ocz3n8d4.fsf@marauder.physik.uni-ulm.de> <87iqpa99wy.fsf@liv.ac.uk> <87wsde7t5j.fsf_-_@marauder.physik.uni-ulm.de> <86mye95p27.fsf@lifelogs.com> <878wpt48qj.fsf@marauder.physik.uni-ulm.de> <86d4eyvryx.fsf@lifelogs.com> <878wplcxws.fsf@marauder.physik.uni-ulm.de> <87k58za3q8.fsf@liv.ac.uk> <87k58zm99o.fsf_-_@marauder.physik.uni-ulm.de> <87fxjn9l7g.fsf@mocca.josefsson.org> <871vv1d50m.fsf@liv.ac.uk> <87wscblcma.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1233503151 25928 80.91.229.12 (1 Feb 2009 15:45:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 1 Feb 2009 15:45:51 +0000 (UTC) To: ding@gnus.org, emacs-devel@gnu.org Original-X-From: ding-owner+M16675@lists.math.uh.edu Sun Feb 01 16:47:05 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LTeX9-0004yG-3W for ding-account@gmane.org; Sun, 01 Feb 2009 16:46:55 +0100 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 1LTeUW-0005fo-47; Sun, 01 Feb 2009 09:44:12 -0600 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 1LTeUU-0005fY-Kr for ding@lists.math.uh.edu; Sun, 01 Feb 2009 09:44:10 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LTeUR-0001ex-KJ for ding@lists.math.uh.edu; Sun, 01 Feb 2009 09:44:10 -0600 Original-Received: from mail44.e.nsc.no ([193.213.115.44]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LTeUk-0003xo-00 for ; Sun, 01 Feb 2009 16:44:26 +0100 Original-Received: from home.famsolberg.com (ti0187a340-dhcp0065.bb.online.no [88.90.247.66]) by mail44.nsc.no (8.13.8/8.13.5) with ESMTP id n11FhWtE017020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 1 Feb 2009 16:43:33 +0100 (MET) Original-Received: from home.famsolberg.com (maui53 [127.0.0.1]) by home.famsolberg.com (8.13.8/8.13.8) with ESMTP id n11FhWRV019832; Sun, 1 Feb 2009 07:43:32 -0800 Original-Received: (from bhso@localhost) by home.famsolberg.com (8.13.8/8.13.8/Submit) id n11FhWLx019831; Sun, 1 Feb 2009 07:43:32 -0800 In-Reply-To: <87wscblcma.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 31 Jan 2009 16:27:25 +0100") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.50 (gnu/linux) X-Spam-Score: -2.4 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68234 gmane.emacs.devel:108522 Archived-At: Reiner Steib writes: > On Sat, Jan 17 2009, Dave Love wrote: >> Simon Josefsson writes: >> >>> Maybe the problem is a condition-case within another condition-case >>> work? I recall problems related to this when run as an async process >>> filter. >> >> Yes -- signals from process filters are normally caught; I wasn't >> thinking or looking closely enough at what the code does originally. I >> must have had debug-on-error set when testing, but I was sure I'd >> actually tried it in fresh Emacs. >> >>> Maybe it is possible to re-write the approach without using >>> condition-case, that would likely be easier to debug anyway. >> >> I'm not sure it would be easier, but see the comment in the patch below. >> I made it before reading this, and at least the fix over my previous >> code is just an extra binding. It works for me in a fresh Emacs, and >> isn't broken in Emacs 22. >> >>> I'd prefer to avoid sending the Exchange bug-workaround approach >>> ("1,*:*") to any server that does not need it. I've seen servers that >>> (internally) open up all e-mails in the folder and searches them, but >>> for the 1,* approach was able to return data quickly. >> >> Obviously that's a good reason. Previous comments about efficiency that >> I was referred to seemed to be about something different. >> >>> This may be old information now, but generally I don't see why >>> imap.el should send poor protocol output to all servers just >>> because Exchange is broken. >> >> [It does have workarounds for various other servers, not that I want to >> defend Exchange in any way. Exchange 2007 is doing horrible things like >> messing with MIME parts, which I don't think the previous version did, >> and I wish I could avoid it.] >> >> Anyhow, per the comment in the patch, > + ;; FIXME: Maybe it would be cleaner to have a flag to not signal > + ;; the error (which otherwise gives a message), and test > + ;; `imap-failed-tags'. Also, Other IMAP clients use other forms of > + ;; request which work with Exchange, e.g. Claws does "UID FETCH 1:* > + ;; (UID)" rather than "FETCH UID 1,*". Is there a good reason not > + ;; to do the same? >> is there a good reason -- other than simplicity? -- to use FETCH >> rather than UID like other clients? I'm speaking mostly in >> ignorance of IMAP... > Comments? (Simon?) >> 2009-01-17 Dave Love >> >> * imap.el (imap-fetch-safe): Bind debug-on-error. >> (imap-debug): Add imap-fetch-safe. > Installed. > Bjorn (and others), does the auto-detection work for you with the > current version from CVS? I just did a "cvs update" in trunk. First off, I get the following message byte-code: Error in ~/.gnus: Please use `smtpmail.el' bundled with Emacs. as smtpmail.el got restored in the contrib directory when I did the cvs update. But other than that, Gnus now starts up fine with no need to set imap-enable-exchange-bug-workaround to t. Thanks, Bjorn.