Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1140
 
9-81
Cisco AsyncOS 8.5.5 for Email Security User Guide
 
Chapter 9      Using Message Filters to Enforce Email Policies
  Using the CLI to Manage Message Filters
Filter with a non-unique filtname
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. 
Deleting a Message Filter
delete [seqnum|filtname|range]
Deletes the filter(s) identified. 
The following conditions can cause errors:
No filter with a given filter name. 
No filter with a given sequence number. 
Moving a Message Filter
move [seqnum|filtname|range seqnum|last]
Moves the filters identified by the first parameter to the position identified by the second parameter. If 
the second parameter is the keyword 
last
, the filters are moved to the end of the list of filters. If more 
than one filter is being moved, their ordering remains the same in relation to one another. 
The following conditions can cause errors:
No filter with a given filter name. 
No filter with a given sequence number. 
Sequence number beyond the current range of sequence numbers. 
Movement would result in no change of sequence. 
Activating and Deactivating a Message Filter
A given message filter is either active or inactive and it is also either valid or invalid. A message filter 
is only used for processing if it is both active and valid. You change an existing filter from active to 
inactive (and back again) via the CLI. A filter is invalid if it refers to a listener or interface which does 
not exist (or has been removed).
Note
You can determine if a filter is inactive by its syntax; AsyncOS changes the colon after the filter name 
to an exclamation point for inactive filters. If you use this syntax when entering or importing a filter, 
AsyncOS marks the filter as inactive.