IronPort - advanced configuration guide

Chapter 6 Using Message Filters to Enforce Email Policies
Receiving Listener Rule
Receiving IP Interface Rule
Date Rule
OL-25137-01
The allowed hosts notation can only identify sequences and numeric ranges of IP addresses (not
hostnames). For example, the following filter bounces any message not injected from IP addresses of
form 10.1.1.x where X is 50, 51, 52, 53, 54, or 55.
notMineFilter:
if (remote-ip != '10.1.1.50-55')
{
}
bounce();
The recv-listener rule selects those messages received on the named listener. The listener name must
be the nickname of one of the listeners currently configured on the system. For example, the following
filter immediately delivers any message arriving from the listener named expedite.
expediteFilter:
if (recv-listener == 'expedite')
{
skip_filters();
}
The recv-int rule selects those messages received via the named interface. The interface name must be
the nickname of one of the interfaces currently configured for the system. For example, the following
filter bounces any message arriving from the interface named outside.
outsideFilter:
if (recv-int == 'outside')
{
}
bounce();
The date rule checks the current time and date against a time and date you specify. The date rule is
compares against a string containing a timestamp of the format
MM/DD/YYYY hh:mm:ss. This is useful to specify actions to be performed before or after certain times
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
6-25