From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: Mat Marcus <mat-lists@emarcus.org>
Cc: ding@gnus.org
Subject: Re: gnus IMAP vs. Exchange Server 2007
Date: Wed, 24 Sep 2008 08:21:52 +0200 [thread overview]
Message-ID: <m3abdydpxb.fsf@gravicappa.englab.brq.redhat.com> (raw)
In-Reply-To: <loom.20080923T204525-422@post.gmane.org> (Mat Marcus's message of "Tue, 23 Sep 2008 20:52:00 +0000 (UTC)")
Mat Marcus <mat-lists@emarcus.org> writes:
> At work, we recently "upgraded" from MS Exchange Server 2003 to 2007. Suddenly
> gnus stopped working as an IMAP client. As Thunderbird also had problems I
> decided to do a little debugging. After viewing the *imap-log* I noticed that in
> the course of the seesion, gnus sends the command
>
> 124 FETCH 1,* UID
>
> to which MS Exchange Server 2007
>
> 124 BAD The specified message set is invalid.
>
> Things go downhill from there. I also manually telneted in and issued the same
> command, and received the same result. My questions are:
>
> 1) is 124 FETCH 1,* UID a valid IMAP command for non-empty mailboxes?
> 2) if so, is this an MS Exchange Server 2007 bug?
> 3) in either case is there a patch workaround for gnus? I am currently running
> gnus "5.11" that comes with emacs 22.1.1.
>
> Sorry if this has already been covered--I am not an expert in IMAP protocols,
> Exchange Server, or gnus.
(setq imap-enable-exchange-bug-workaround t)
"Documentation:
Send FETCH UID commands as *:* instead of *.
Enabling this appears to be required for some servers (e.g.,
Microsoft Exchange) which otherwise would trigger a response 'BAD
The specified message set is invalid.'."
--
wbr, Vitaly
next prev parent reply other threads:[~2008-09-24 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 20:52 Mat Marcus
2008-09-24 6:21 ` Vitaly Mayatskikh [this message]
2008-09-24 7:28 ` David Engster
2008-09-24 17:07 ` Mat Marcus
2008-09-24 18:13 ` Vitaly Mayatskikh
2008-09-24 18:27 ` Reiner Steib
2008-09-24 20:25 ` Steinar Bang
2008-09-25 17:31 ` Mat Marcus
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=m3abdydpxb.fsf@gravicappa.englab.brq.redhat.com \
--to=v.mayatskih@gmail.com \
--cc=ding@gnus.org \
--cc=mat-lists@emarcus.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.
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 NNTP newsgroup(s).