Cisco Cisco Email Security Appliance C160 Betriebsanweisung
9-62
Cisco AsyncOS 8.5.6 for Email User Guide
Chapter 9 Using Message Filters to Enforce Email Policies
Message Filter Actions
Notification Template
You can use the Text Resources page or the
textconfig
CLI command to configure custom notification
templates as text resources for use with the
notify()
and
notify-copy()
actions. If you do not create a
custom notification template, a default template is used. The default template includes message headers,
but the custom notification template does not include message headers by default. To include message
headers in the custom notification, include the
but the custom notification template does not include message headers by default. To include message
headers in the custom notification, include the
$AllHeaders
action variable.
For more information, see the “Text Resources” chapter.
In the following example, when a large message triggers the filter shown below, an email is sent to the
intended recipients explaining that the message was too large:
intended recipients explaining that the message was too large:
Blind Carbon Copy Actions
The
bcc
action sends an anonymous copy of the message to a specified recipient. This is sometimes
referred to as message replication. Because no mention of the copy is made in the original message and
the anonymous copy will never successfully bounce back to the recipient, the original sender and
recipients of the message will not necessarily know that the copy was sent.
the anonymous copy will never successfully bounce back to the recipient, the original sender and
recipients of the message will not necessarily know that the copy was sent.
The following filter sends a blind carbon copy to
mom@home.org
for each message addressed to
sue
from
johnny
:
The
bcc
action also supports up to three additional, optional arguments that allow you to specify the
subject header and Envelope Sender to use on the copied message, as well as an alt-mailhost. These
parameters must appear in order, so a subject must be provided if the Envelope Sender is to be set.
parameters must appear in order, so a subject must be provided if the Envelope Sender is to be set.
The subject parameter may contain action variables (see
) that will be
replaced with data from the original message. By default, this is set to the subject of the original message
(the equivalent of
(the equivalent of
$Subject
).
bigFilter:
if (body-size >= 4M)
{
notify('$EnvelopeRecipients', '[$FilterName] Message too large',
'$EnvelopeFrom', 'message.too.large');
drop();
}
momFilter:
if ((mail-from == '^johnny$') and (rcpt-to == '^sue$'))
{
bcc('mom@home.org');
}