Cisco Cisco Email Security Appliance C160 Références techniques

mail3.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 encodings bodies and footers: Use encoding of message 

footer

Choose the operation you want to perform:

- SETUP - Configure multi-lingual settings.

[]> setup

If a header is modified, encode the new header in the same encoding as the 

message body? (Some MUAs incorrectly handle headers encoded in a different 

encoding than the body. However, encoding a modified header in the same encoding 

as the message body may cause certain characters in the modified header to be 

lost.) [Y]>

If a non-ASCII header is not properly tagged with a character set, impose the 

encoding of the body on the header during processing and final representation of 

the message? (Many MUAs create non-RFC-compliant headers that are then handled in 

an undefined way. Imposing the encoding of the body on the header may encode the 

header more precisely.) [Y]>

When there is an encoding mismatch between the message body and a footer, the 

system initially attempts to encode the entire message in the same encoding as 

the message body. If the system cannot combine the message body and the footer in 

the same encoding, do you want the system to failover and attempt to encode the 

entire message using the encoding of the message footer? (When this feature is 

enabled, the system will attempt to display the footer "in-line" rather than 

defaulting to adding it as an attachment.) [N]> y

Behavior when modifying headers: Use encoding of message body

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

Choose the operation you want to perform: