Cisco Cisco Email Security Appliance C160 User Guide

Typically, when there is an encoding mismatch between the message body and a 
disclaimer, AsyncOS attempts to encode the entire message in the same encoding 
as the message body so that the disclaimer will be included in the body (“inline”) 
and not included as a separate attachment. In other words, the disclaimer will be 
included inline if the encoding of the disclaimer matches that of the body, or if the 
text in the disclaimer contains characters that can be displayed inline (in the 
body). For example, it is possible to have a ISO-8859-1 encoded disclaimer that 
only contains US-ASCII characters; consequently, this will display “inline” 
without problems.

However, if the disclaimer cannot be combined with the body, you can use the 

localeconfig

 command to configure AsyncOS to attempt to promote, or convert, 

the body text to match the encoding of the disclaimer so that the disclaimer can 
be included in the body of the message:

Example.zip

First attachment part

example.com> localeconfig

Behavior when modifying headers: Use encoding of message body

Behavior for untagged non-ASCII headers: Impose encoding of message body

Behavior for mismatched footer or heading encoding: Only try encoding 

from

message body

Choose the operation you want to perform:

- SETUP - Configure multi-lingual settings.

[]> setup