Cisco Cisco Email Security Appliance C170 사용자 가이드

AsyncOS attempts to determine the charset of a message based on the encoding specified in the message 
headers. However, if the encoding specified in the headers does not match that of the actual text, the 
message will not be displayed properly when viewed in the Cisco IronPort Spam quarantine. This 
situation is more likely to occur with spam messages.

In the case where incoming email does not have a charset encoding specified in the headers, you can 
configure your Cisco IronPort appliance to specify a default encoding. Doing so will help ensure that 
these types of messages display properly in the Cisco IronPort Spam quarantine.

However, specifying a default encoding can cause messages in other charsets to display incorrectly. This 
applies only to messages that do not specify the encoding in the message headers. Generally, you would 
only want to set a default encoding if you expect the majority of your mail that falls into this category 
to be of one specific encoding. For example, if the majority of your mail that gets quarantined and that 
does not specify the charset encoding in the message headers is in Japanese (ISO-2022-JP), you would 
select option 12 (in the 

scanconfig->setup 

options, below) when prompted: 

Configure encoding to 

use when none is specified for plain body text or anything with MIME type plain/text or 

plain/html.

To set a default encoding for messages that do not specify the encoding in the message headers, use the 

scanconfig->setup

 command via the CLI. In this example, UTF-8 is set as the default:

mail3.example.com> scanconfig

There are currently 7 attachment type mappings configured to be SKIPPED.

Choose the operation you want to perform:

- NEW - Add a new entry.

- DELETE - Remove an entry.

- SETUP - Configure scanning behavior.

- IMPORT - Load mappings from a file.

- EXPORT - Save mappings to a file.

- PRINT - Display the list.

- CLEAR - Remove all entries.

[]> setup

[ ... ]