Cisco Cisco Email Security Appliance C160 Mode D'Emploi

The following conditions can cause errors:

No filter with a given filtname.

No filter with a given sequence number. 

A filter which is inactive may also be noted in its syntax; the colon after the label (name of the filter) is 
changed to an exclamation point (

!

). A filter entered manually from the CLI, or imported, that contains 

this syntax, will automatically be marked inactive. For example, 

mailfrompm!

 instead of 

mailfrompm:

 is 

displayed.

import filename

The name of the file containing filters to be processed. This file must reside in the 

 

configuration directory of the FTP/SCP root directory on the appliance, if you enabled FTP/SCP access 
for the interface with the 

interfaceconfig

 command. It is ingested and parsed, and any errors are 

reported. The filters imported replace all filters existing in the current filter set. See 

 for more information. Consider exporting the current filter list (see 

) and then editing that file before importing.

When importing message filters, you are prompted to select the encoding used.

The following conditions can cause errors:

File does not exist.

Filter with a non-unique filter name. 

Filter with a filtname that is a reserved word. 

Filter with a syntax error. 

Filter with actions referring to non-existent system resources such as interfaces. 

export filename [seqnum|filtname|range]

Output a formatted version of the existing filter set to a file in the configuration directory of the FTP/SCP 
root directory on the appliance. See 

 for more information.

When exporting message filters, you are prompted to select the encoding used.

The following conditions can cause errors:

No filter with a given filter name. 

No filter with a given sequence number. 

The system displays filters containing non-ASCII characters in the CLI in UTF-8. If your 
terminal/display does not support UTF-8, the filter will unreadable.