M2 IMAP confuses Exchange (9.60RC)

[Dirk Fieldhouse <fieldhouse@xxxxxxx>]

Although 9.60RC is indeed nippy, I'm seeing a problem with its IMAP handling 
used to access a Microsoft Exchange server.

The server announces itself as follows

* OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (host) 
ready.
00EV CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS MAILBOX-REFERRALS NAMESPACE 
LITERAL+ UIDPLUS CHILDREN
00EV OK CAPABILITY completed.

When fetching new messages an error "One of the supplied fetch items is 
invalid" occurs as in the following redacted Wireshark grab (note also that M2 
is not announcing its version number correctly yet):

...
009V UID FETCH 2523 (UID BODY.PEEK[] FLAGS)
* 2232 FETCH (UID 2523 BODY[] {3394}
Date: Thu, 11 Sep 2008 14:37:38 +0100
To: someone
Subject: something
From: me
Organization: my company
Cc: my colleagues
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
...
User-Agent: Opera Mail/9.52 (Win32)

the message text
for quite a few lines
until the end
 FLAGS (\Seen))
009V OK FETCH completed.
009W UID FETCH 2182 (UID RFC822.SIZE BODY.PEEK[HEADER.FIELDS (SUBJECT FROM TO 
CC REPLY-TO DATE MESSAGE-ID REFERENCES IN-REPLY-TO LIST-ID LIST-POST 
X-MAILING-LIST DELIVERED-TO X-SPAM-SCORE RECEIVED (FROM|REPLY-TO) DELIVERED-TO 
X-RESENT-TO LIST-ID SENDER)] BODYSTRUCTURE FLAGS)
009W BAD Protocol Error: "One of the supplied fetch items is invalid".
...

Mmmmm, that IMAP is one neat protocol, or would be if it worked !

I suspect that Exchange is lying about its capabilities but as it's a common 
server M2 ought to work around this.

My environment:

Version 9.60 beta
Build   10424
Platform        Win32
System  Windows 98

/df