IronPort - advanced configuration guide

Chapter 6 Using Message Filters to Enforce Email Policies
OL-25137-01
The Envelope Recipient parameter may be any valid email address (for example, admin@example.com in
the example above), or alternatively, may be the action variable $EnvelopeRecipients (see Action
Variables, page 6-48), which specifies all Envelope Recipients of the message:
bigFilter:
if(body-size >= 4M)
{
}
The notify action also supports up to three additional, optional arguments that allow you to specify the
subject header, the Envelope Sender, and a pre-defined text resource to use for the notification message.
These parameters must appear in order, so a subject must be provided if the Envelope Sender is to be set
or a notification template specified.
The subject parameter may contain action variables (see Action Variables, page 6-48) that will be
replaced with data from the original message. By default, the subject is set to Message Notification.
The Envelope Sender parameter may be any valid email address, or alternatively, may be the action
variable $EnvelopeFrom, which will set the return path of the message to the same as the original
message
The notification template parameter is the name of an existing notification template. For more
information, see Notifications, page 6-72.
This example extends the previous one, but changes the subject to look like [bigFilter] Message too
large, sets the return path to be the original sender, and uses the “message.too.large” template:
bigFilter:
notify('$EnvelopeRecipients');
drop();
if (body-size >= 4M)
{
}
notify('admin@example.com', '[$FilterName] Message too large',
drop();
'$EnvelopeFrom', 'message.too.large');
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
6-53