Differences between revisions 3 and 4
Revision 3 as of 2011-10-04 14:49:12
Size: 618
Editor: TimoSirainen
Comment:
Revision 4 as of 2011-10-04 14:49:39
Size: 629
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
Exchange sometimes messes up sequence <-> UID mapping. Especially when doing a "UID FETCH n:* FLAGS" immediately after a new mail has arrived (EXISTS reply was received) it often sends sequences higher than the EXISTS reply and also sends UIDs belonging to wrong (existing) sequences. Exchange sometimes messes up sequence <-> UID mapping. Especially when doing a "UID FETCH n:* FLAGS" immediately after a new mail has arrived (EXISTS reply was received) it often sends sequences higher than the EXISTS reply and also sends UIDs belonging to wrong (existing) sequences. (2010 SP1)

Microsoft Exchange Bugs

IMAP requires messages to be immutable. Exchange IMAP changes the existing mails sometimes:

  • Exchange adds/removes/updates X-Message-Flag: header. At least \Flagged IMAP flag modifies it. (2010 SP1)
  • When user's name changes, the name in existing messages' headers are modified. (2010 SP1)

Exchange sometimes messes up sequence <-> UID mapping. Especially when doing a "UID FETCH n:* FLAGS" immediately after a new mail has arrived (EXISTS reply was received) it often sends sequences higher than the EXISTS reply and also sends UIDs belonging to wrong (existing) sequences. (2010 SP1)

ServerBugs/MSExchange (last edited 2011-10-04 14:49:39 by TimoSirainen)