From: Bjorn Solberg <bjorn_ding2@hekneby.org>
To: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: IMAP and Exchange 2007 - imap-fetch-safe
Date: Sun, 01 Feb 2009 07:43:32 -0800 [thread overview]
Message-ID: <m3fxiy17tn.fsf@famsolberg.com> (raw)
In-Reply-To: <87wscblcma.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 31 Jan 2009 16:27:25 +0100")
Reiner Steib writes:
> On Sat, Jan 17 2009, Dave Love wrote:
>> Simon Josefsson <simon@josefsson.org> 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 <fx@gnu.org>
>>
>> * 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.
next prev parent reply other threads:[~2009-02-01 15:43 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 ` IMAP and Exchange 2007 - imap-fetch-safe Simon Josefsson
2009-01-17 20:58 ` Dave Love
2009-01-31 15:27 ` Reiner Steib
2009-02-01 15:43 ` Bjorn Solberg [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fxiy17tn.fsf@famsolberg.com \
--to=bjorn_ding2@hekneby.org \
--cc=ding@gnus.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.