Initial situation:

The use of a text encoding other than UTF-8 may cause problems at one of the email-processing relays.

 

Effect:

Incoming:

Due to the possible new encoding at an upstream relay, emails may no longer be decrypted at the SEPPmail Secure E-Mail Gateway and/or attached signatures may have been destroyed by the change.

 

Individual remedy:

If possible, do not execute any new encoding on upstream relays.

 

Outgoing:

With outgoing emails, formatting problems with disclaimers to be attached may occur.

 

Cause:

Generally, Outlook always uses the minimal charset required. For instance, if no umlauts (or other special characters) are present in the email, the charset us-ascii will be used.

Since the SEPPmail Secure E-Mail Gateway keeps its manipulations of emails to a min, when using the disclaimer function, any umlauts or special characters contained in the disclaimer would be converted to the already existing charset. This can only lead to the incorrect representation of these special characters.

 

Individual remedy:

1.For Outlook: Set the use of UTF-8 as default (if applicable in the AD via GPO)
 

2.Use email clients which are generally adapted to the national language by default (e.g. Thunderbird) and which generally use UTF-8.
 

3."Force UTF-8" Use settings of the SEPPmail Secure E-Mail Gateway (see EDIT DISCLAIMER Disclaimer settings Advanced).