[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IMAP and Exchange 2007 - imap-fetch-safe
From: |
Simon Josefsson |
Subject: |
Re: IMAP and Exchange 2007 - imap-fetch-safe |
Date: |
Tue, 13 Jan 2009 18:20:35 +0100 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) |
Reiner Steib <address@hidden> 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