3 steps to correct message encoding in emails
Regional characters (such as ü, ä, ø, etc.) in signatures and disclaimers added by CodeTwo Exchange Rules are not displayed correctly. Instead of the actual characters, users see strings of ? signs.
This issue is most likely caused by incorrect encoding settings. For example, the proper display of European regional characters requires the UTF-8 encoding protocol (Central European). If the encoding in your environment is set, for example to ASCII, the regional characters will not be displayed correctly.
If ? appears instead of a regional character, force the correct encoding settings in:
- Windows Server
- 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). This will allow you to automatically convert all plain text emails to HTML. Since the encoding issue is almost exclusive to TXT-formatted messages, the problem should be solved. All regional characters will be correctly displayed, regardless of the encoding settings.
Applies to CodeTwo Exchange Rules 2013 1.x | 2010 1.x and 2.x | 2007 2.x and 3.x, and CodeTwo Signatures for Email Clients
If you designed your signature outside the Editor, locate the file containing the signature and open it, for example, in Windows Notepad. Click File > Save as and make sure that the encoding is set correctly (Fig. 1.). Upload the corrected file to the Editor.
|Related products:||CodeTwo Email Signatures for Email Clients, CodeTwo Email Signatures for Office 365 1.x, CodeTwo Exchange Rules 2.x, 3.x, CodeTwo Exchange Rules 2007 1.x, 2.x, 3.x, 4.x, CodeTwo Exchange Rules 2010 1.x, 2.x, 3.x, CodeTwo Exchange Rules 2013 1.x, 2.x, CodeTwo Exchange Rules 2016 1.x, CodeTwo Exchange Rules 2019 1.x, CodeTwo Exchange Rules Pro 1.x, 2.x|