27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

OL-25137-01<br />

Filter with a syntax error.<br />

Deleting a Message Filter<br />

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

delete [seqnum|filtname|range]<br />

Deletes the filter(s) identified.<br />

Moving a Message Filter<br />

The following conditions can cause errors:<br />

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

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

move [seqnum|filtname|range seqnum|last]<br />

Moves the filters identified by the first parameter to the position identified by the second parameter. If<br />

the second parameter is the keyword last, the filters are moved to the end of the list of filters. If more<br />

than one filter is being moved, their ordering remains the same in relation to one another.<br />

The following conditions can cause errors:<br />

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

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

Sequence number beyond the current range of sequence numbers.<br />

Movement would result in no change of sequence.<br />

Activating and Deactivating a Message Filter<br />

A given message filter is either active or inactive and it is also either valid or invalid. A message filter<br />

is only used for processing if it is both active and valid. You change an existing filter from active to<br />

inactive (and back again) via the CLI. A filter is invalid if it refers to a listener or interface which does<br />

not exist (or has been removed).<br />

Note You can determine if a filter is inactive by its syntax; AsyncOS changes the colon after the filter name<br />

to an exclamation point for inactive filters. If you use this syntax when entering or importing a filter,<br />

AsyncOS marks the filter as inactive.<br />

For example, the following benign filter named “filterstatus” is entered. It is then made inactive using<br />

the filter -> set subcommand. Note that when the details of the filter are shown, the colon has been<br />

changed to an exclamation point (and is bold in the following example).<br />

mail3.example.com> filters<br />

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

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

6-77

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

Saved successfully!

Ooh no, something went wrong!