Cisco Cisco Email Security Appliance C160 Guía Del Usuario
9-55
Cisco AsyncOS 8.5.5 for Email Security User Guide
Chapter 9 Using Message Filters to Enforce Email Policies
Message Filter Actions
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
), which specifies all Envelope Recipients of the message:
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.
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
) 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
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
information, see
.
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:
drop();
}
bigFilter:
if(body-size >= 4M)
{
notify('$EnvelopeRecipients');
drop();
}
bigFilter:
if (body-size >= 4M)
{
notify('admin@example.com', '[$FilterName] Message too large',
'$EnvelopeFrom', 'message.too.large');
drop();
}