From: Simon Josefsson <simon@josefsson.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Gnus - Exchange IMAP issues (can't enter INBOX)
Date: Tue, 01 Apr 2008 16:17:58 +0200 [thread overview]
Message-ID: <87od8tpskp.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <867ihjqgf0.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 05 Feb 2008 14:47:31 -0600")
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 Exchange
> TZ> server over IMAP. I can't enter the INBOX, so it's annoying. I haven't
> TZ> seen it before with other Exchange servers, so I don't know if 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.
The command was 'FETCH 1,* UID' and the response was '1775 BAD The
specified message set is invalid.' (btw, a imap-log output log would be
simpler to read than the imap-debug output).
Investigating why the server returns this message in response to that
command would help. Is the mailbox perhaps close to empty? Anyway,
this seems like a server bug to me.
I recall some servers have had problems returning data for 1,* queries
when the mailbox contains zero or one message. Is this the case here?
As far as I can tell, it doesn't seem it is, since the imap-debug output
contains '9 EXISTS' so there should be 9 messages. In that case, I have
no idea why the command fails.
/Simon
next prev parent reply other threads:[~2008-04-01 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 21:18 Ted Zlatanov
2008-02-05 20:47 ` Ted Zlatanov
2008-04-01 14:17 ` Simon Josefsson [this message]
2008-04-01 14:32 ` Jake Colman
2008-04-01 14:50 ` Simon Josefsson
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=87od8tpskp.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).