From: Simon Josefsson <simon@josefsson.org>
To: Dave Love <fx@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org,
Bjorn Solberg <bjorn_ding2@hekneby.org>
Subject: Re: IMAP and Exchange 2007 - imap-fetch-safe
Date: Tue, 13 Jan 2009 18:20:35 +0100 [thread overview]
Message-ID: <87fxjn9l7g.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <87k58zm99o.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 13 Jan 2009 18:00:03 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> It also goes away when I try to debug it. I see the old error sometimes
>> when starting Gnus afresh, and the trace says imap-fetch-safe is called
>> from nnimap-find-minmax-uid. It appears that the condition-case in
>> imap-fetch-safe isn't catching the error thrown by imap-parse-message.
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.
Maybe it is possible to re-write the approach without using
condition-case, that would likely be easier to debug anyway.
>> and it's not clear to me what the problem is with always using the
>> workaround anyhow. Are there servers on which it's known to fail or be
>> noticeably slow?
>
> Simon? Others?
> http://thread.gmane.org/gmane.emacs.gnus.general/66635/focus=94117
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. 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.
/Simon
next prev parent reply other threads:[~2009-01-13 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87iqphil5p.fsf@liv.ac.uk>
[not found] ` <87ocz3n8d4.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87iqpa99wy.fsf@liv.ac.uk>
[not found] ` <87wsde7t5j.fsf_-_@marauder.physik.uni-ulm.de>
[not found] ` <86mye95p27.fsf@lifelogs.com>
[not found] ` <878wpt48qj.fsf@marauder.physik.uni-ulm.de>
[not found] ` <86d4eyvryx.fsf@lifelogs.com>
[not found] ` <878wplcxws.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87k58za3q8.fsf@liv.ac.uk>
2009-01-13 17:00 ` IMAP and Exchange 2007 - imap-fetch-safe (was: FIXMEs in imap.el and nnimap.el) Reiner Steib
2009-01-13 17:20 ` Simon Josefsson [this message]
2009-01-17 20:58 ` IMAP and Exchange 2007 - imap-fetch-safe Dave Love
2009-01-31 15:27 ` Reiner Steib
2009-02-01 15:43 ` Bjorn Solberg
2009-02-02 19:15 ` Reiner Steib
2009-01-13 18:28 ` Bjorn Solberg
2009-01-17 20:59 ` Dave Love
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fxjn9l7g.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=bjorn_ding2@hekneby.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=fx@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).