Re: M2 IMAP confuses Exchange (9.60RC)

[Dirk Fieldhouse <fieldhouse@xxxxxxx>]

In article <i12qd459aeomp44iiomh0jt5sr64rihnl7@xxxxxxx>, 
do.not@xxxxxxxxxxxxxxx says...
>...>
[M2 is asking for all the headers mentioned in 'matches any header' filter 
rules but not dealing with regexp case properly]
>
>This bug should be fixed in the next snapshot.

Excellent; thanks Tim. I've lost the bug ID, but you might want to check the 
following transcript with an "Invalid message format" to see if the same fix 
applies (I've put a _ at the end of wrapped lines):

00MF SELECT "Sent Items"
* 2263 EXISTS
* 0 RECENT
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)]_  
 Permanent flags
* OK [UIDVALIDITY 9273050] UIDVALIDITY value
00MF OK [READ-WRITE] SELECT completed.
00MG 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 DELIVERED-TO X-RESENT-TO_
 LIST-ID SENDER)] BODYSTRUCTURE FLAGS)
00MG NO Invalid message format.
00MH IDLE
+ IDLE accepted, awaiting DONE command.

Does this just mean that (eg) X-SPAM-SCORE is not a header spec'd in RFC2822 
and so not allowed inside HEADER.FIELDS()? In which case it's probably the 
same bug, though perhaps not the same cause.

/df