of Outlook designed for Greece, for example, the default encoding will be. All regional characters will be correctly displayed, regardless of the encoding settings. Forwarding a message will always attempt to put the main message text body. Since the encoding issue is almost exclusive to TXT-formatted messages, the problem should be solved. This will allow you to automatically convert all plain text emails to HTML.
If none of the solutions above helps, you can try a workaround to the encoding issue and use the Force email format action (available only in CodeTwo Exchange Rules Pro). Outlook on the web (only in hybrid deployments with on-premises Exchange server).If ? appears instead of a regional character, force the correct encoding settings in: If the encoding in your environment is set, for example to ASCII, the regional characters will not be displayed correctly. For example, the proper display of European regional characters requires the UTF-8 encoding protocol (Central European). This issue is most likely caused by incorrect encoding settings. Instead of the actual characters, users see strings of ? signs. Regional characters (such as ü, ä, ø, etc.) in signatures and disclaimers added by CodeTwo Exchange Rules are not displayed correctly.
3 steps to correct message encoding in emails MS Outlook Outlook on the web (only in hybrid deployments with on-premises Exchange server) If none of the solutions above helps, you can try a workaround to the encoding issue and use the Force email format action (available only in CodeTwo Exchange Rules Pro).
