Cisco Cisco Email Security Appliance C190 Guida Utente

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 and 

is being used or modified, 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. Some MUAs handle headers encoded in character sets 

that differ from that of the main body in an incorrect way. Imposing the encoding of the 

body on the header may encode

the header more precisely. This will be used to interpret the content of headers for 

processing, it will not modify or rewrite the header

 unless that is done explicitly as part of the processing.) [Y]>

Footers or headings are added in-line with the message body whenever 

possible. However, if the footer or heading is encoded differently 

than the message body,and if imposing a single encoding will cause 

loss of characters, it will be added as an attachment. The system will 

always try to use the message body's encoding for the footer or 

heading. If that fails, and if the message body's encoding is US-

ASCII, the system can try to edit the message body to use the footer's 

or heading's encoding. Should the system try to impose the footer's 

or headings's encoding on the message body? [N]> y

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: Try both 

body and footer or heading encodings

Choose the operation you want to perform: