27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

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

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

Chapter 6 Using Message Filters to Enforce Email Policies<br />

OL-25137-01<br />

The following conditions can cause errors:<br />

No filter with a given filtname.<br />

No filter with a given sequence number.<br />

Note A filter which is inactive may also be noted in its syntax; the colon after the label (name of the filter) is<br />

changed to an exclamation point (!). A filter entered manually from the CLI, or imported, that contains<br />

this syntax, will automatically be marked inactive. For example, mailfrompm! instead of mailfrompm: is<br />

displayed.<br />

Importing Message Filters<br />

import filename<br />

The name of the file containing filters to be processed. This file must reside in the<br />

<strong>configuration</strong> directory of the FTP/SCP root directory on the appliance, if you enabled FTP/SCP access<br />

for the interface with the interfaceconfig command. It is ingested and parsed, and any errors are<br />

reported. The filters imported replace all filters existing in the current filter set. See Appendix B,<br />

“Accessing the Appliance” for more information. Consider exporting the current filter list (see Exporting<br />

Message Filters, page 6-81) and then editing that file before importing.<br />

When importing message filters, you are prompted to select the encoding used.<br />

The following conditions can cause errors:<br />

File does not exist.<br />

Filter with a non-unique filter name.<br />

Filter with a filtname that is a reserved word.<br />

Filter with a syntax error.<br />

Exporting Message Filters<br />

Filter with actions referring to non-existent system resources such as interfaces.<br />

export filename [seqnum|filtname|range]<br />

Output a formatted version of the existing filter set to a file in the <strong>configuration</strong> directory of the FTP/SCP<br />

root directory on the appliance. See Appendix B, “Accessing the Appliance” for more information.<br />

When exporting message filters, you are prompted to select the encoding used.<br />

The following conditions can cause errors:<br />

No filter with a given filter name.<br />

No filter with a given sequence number.<br />

Viewing Non-ASCII Character Sets<br />

The system displays filters containing non-ASCII characters in the CLI in UTF-8. If your<br />

terminal/display does not support UTF-8, the filter will unreadable.<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

6-81

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

Saved successfully!

Ooh no, something went wrong!