IronPort - advanced configuration guide

Notifications
6-72
Step 9 Submit and commit your changes.
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
Chapter 6 Using Message Filters to Enforce Email Policies
Using the Text Resources page in the GUI or the textconfig CLI command to configure custom
notification templates as text resources is another useful tool when used in conjunction with attachment
filtering rules. The notification template supports non-ASCII characters (you are prompted to choose an
encoding while creating the template).
In the following example, the textconfig command was first used to create a notification template
named strip.mp3 that will be inserted into to the body of the notification message. Then, an attachment
filtering rule is created so that when an .mp3 file has been stripped from a message, a notification email
is sent to the intended recipients explaining that the .mp3 file has been deleted.
For more information, see Notify and Notify-Copy Actions, page 6-52.
Examples of Attachment Scanning Message Filters
Inserting Headers
drop-mp3s:
if (attachment-type == '*/mp3')
{ drop-attachments-by-filetype('Media');
notify ('$EnvelopeRecipients', 'Your mp3 has been removed', '$EnvelopeFrom',
'strip.mp3');
}
The following examples shows actions performed on attachments.
In these examples, AsyncOS inserts headers when the attachments contain specified content.
In the following example, all of the attachments on the message are scanned for a keyword. If the
keyword is present in all of the attachments, a custom X-Header is inserted:
attach_disclaim:
if (every-attachment-contains('[dD]isclaimer') ) {
}
insert-header("X-Example-Approval", "AttachOK");
OL-25137-01