27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring the Cisco <strong>IronPort</strong> Spam Quarantines Feature<br />

Default Encoding<br />

Specifying a Default Encoding<br />

4-34<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email Daily Management Guide<br />

Chapter 4 Quarantines<br />

<strong>AsyncOS</strong> attempts to determine the charset of a message based on the encoding specified in the message<br />

headers. However, if the encoding specified in the headers does not match that of the actual text, the<br />

message will not be displayed properly when viewed in the Cisco <strong>IronPort</strong> Spam quarantine. This<br />

situation is more likely to occur with spam messages.<br />

In the case where incoming email does not have a charset encoding specified in the headers, you can<br />

configure your Cisco <strong>IronPort</strong> appliance to specify a default encoding. Doing so will help ensure that<br />

these types of messages display properly in the Cisco <strong>IronPort</strong> Spam quarantine.<br />

However, specifying a default encoding can cause messages in other charsets to display incorrectly. This<br />

applies only to messages that do not specify the encoding in the message headers. Generally, you would<br />

only want to set a default encoding if you expect the majority of your mail that falls into this category<br />

to be of one specific encoding. For example, if the majority of your mail that gets quarantined and that<br />

does not specify the charset encoding in the message headers is in Japanese (ISO-2022-JP), you would<br />

select option 12 (in the scanconfig->setup options, below) when prompted: Configure encoding to<br />

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

plain/html.<br />

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

scanconfig->setup command via the CLI. In this example, UTF-8 is set as the default:<br />

mail3.example.com> scanconfig<br />

There are currently 7 attachment type mappings configured to be SKIPPED.<br />

Choose the operation you want to perform:<br />

- NEW - Add a new entry.<br />

- DELETE - Remove an entry.<br />

- SETUP - Configure scanning behavior.<br />

- IMPORT - Load mappings from a file.<br />

- EXPORT - Save mappings to a file.<br />

- PRINT - Display the list.<br />

- CLEAR - Remove all entries.<br />

[]> setup<br />

[ ... ]<br />

OL-25138-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!