Some examples from OWA. Hrm.

https://shrewdness.ximian.com:4430/exchange/danw/Inbox/[Evolution-patches]%2014705%20(outlook%20isn%27t%20even%20imip%20compatible%20with%20itself).EML/1_multipart/2_text.txt

https://shrewdness.ximian.com:4430/exchange/danw/Inbox/[Fwd:%20RE:%20[Betamanager-swisscom]%20Yep%20_x003F_].EML/1_multipart_xF8FF_2_Forwarded%20message%20-%20RE%253A%20[Betamanager-swisscom]%20Yep%20%253F.eml

https://shrewdness.ximian.com:4430/exchange/danw/Inbox/[Ximian%20Gene-pool]%20New%20Development%20Plan%20document.EML/1_multipart/2_text.txt

https://shrewdness.ximian.com:4430/exchange/danw/Inbox/invoice.EML/1_multipart/2_application.gz

The new X-MS-ENUMATTS method in Exchange 2003 will let us do this.

evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago.

evolution-exchange is now deprecated and not under active development anymore.

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.

Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported.
Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.