Re: Gnus - Exchange IMAP issues (can't enter INBOX)

[Simon Josefsson <simon@josefsson.org>]

Jake Colman <colman@ppllc.com> writes:

>>>>>> "SJ" == Simon Josefsson <simon@josefsson.org> writes:
>
>    SJ> Ted Zlatanov <tzz@lifelogs.com> writes:
>    >> On Mon, 28 Jan 2008 15:18:19 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
>    >> 
>    TZ> I get an interesting error when trying to refresh INBOX on a MS
>    SJ> Exchange
>    TZ> server over IMAP.  I can't enter the INBOX, so it's annoying.  I
>    SJ> haven't
>    TZ> seen it before with other Exchange servers, so I don't know if
>    SJ> something
>    TZ> is misconfigured on my end...
>    >> 
>    >> Since no one had ideas, I had to switch to nnmaildir and IMAP fetching
>    >> (hence the mail-source.el patch I posted earlier).  Too bad, I'd still
>    >> like to understand why Exchange rejected simple IMAP commands and
>    >> Thunderbird works fine with the same server.
>
>    SJ> The command was 'FETCH 1,* UID' and the response was '1775 BAD The
>    SJ> specified message set is invalid.' (btw, a imap-log output log would be
>    SJ> simpler to read than the imap-debug output).
>
> Which variable turns that one?  I only saw the imap-debug variable.

Try 'imap-log'.

>    SJ> Investigating why the server returns this message in response to that
>    SJ> command would help.  Is the mailbox perhaps close to empty?  Anyway,
>    SJ> this seems like a server bug to me.
>
>    SJ> I recall some servers have had problems returning data for 1,* queries
>    SJ> when the mailbox contains zero or one message.  Is this the case here?
>
> No, not at all.  Hmmm.  Actually, it does split my INBOX correctly, at
> which point INBOX is empty.  Could that be what's triggering the problem?

I couldn't tell, and even if it is, it would still only be a bug in the
server.  There is now a workaround for this bug in the code, so I think
without more evidence or patches we can't do anything more.

/Simon