Assume that you are in a Microsoft Exchange Server 2013 or Exchange Server 2016 environment, and then you use an Exchange ActiveSync (EAS) SmartForward or SmartReply command, such as by replying to the message from an iOS client, on a message that contains UTF-8 surrogate pairs, such as emoji. In the sent response, the UTF-8 surrogate pairs in the replied or forwarded message are displayed as question marks.


This issue occurs because when the body is copied to the response message, charset detection incorrectly detects the body as US-ASCII instead of UTF-8, and HTML escaping with US-ASCII conversions does not correctly process surrogate pairs.


To fix this issue, install one of the following cumulative updates:


To work around this issue, reply to the message by using another protocol or endpoint.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!