27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Recipient Count Rule<br />

Address Count Rule<br />

Body Scanning Rule<br />

6-28<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

Chapter 6 Using Message Filters to Enforce Email Policies<br />

The rcpt-count rule compares the number of recipients of a message against an integer value, in a<br />

similar way to the body-size rule. This can be useful for preventing users from sending email to large<br />

numbers of recipients at once, or for ensuring that such large mailing campaigns go out over a certain<br />

Virtual Gateway address. The following example sends any email with more than 100 recipients over a<br />

specific Virtual Gateway address:<br />

large_list_filter:<br />

if (rcpt-count > 100) {<br />

}<br />

alt-src-host('mass_mailing_interface');<br />

The addr-count() message filter rule takes one or more header strings, counts the number of recipients<br />

in each line and reports the cumulative number of recipients. This filter differs from the rcpt-count<br />

filter rule in that it operates on the message body headers instead of the envelope recipients. The<br />

following example shows the filter rule used to replace a long list of recipients with the alias,<br />

“undisclosed-recipients”:<br />

count: if (addr-count("To", "Cc") > 30) {<br />

}<br />

strip-header("To");<br />

strip-header("Cc");<br />

insert-header("To", "undisclosed-recipients");<br />

The body-contains() rule scans the incoming email and all its attachments for a particular pattern<br />

defined by its parameter. This includes delivery-status parts and associated attachments. The<br />

body-contains() rule does not perform multi-line matching. The scanning logic can be modified using<br />

the scanconfig command in the CLI to define which MIME types should or should not be scanned. You<br />

can also specify a minimum number of matches that the scanning engine must find in order for the scan<br />

to evaluate to true.<br />

By default, the system scans all attachments except for those with a MIME type of video/*, audio/*,<br />

image/*. The system scans archive attachments — .zip, .bzip, .compress, .tar, or .gzip attachments<br />

containing multiple files. You can set the number of “nested” archived attachments to scan (for example,<br />

a .zip contained within a .zip).<br />

For more information, including an example of how to use the scanconfig command to set the<br />

attachment scanning behavior, see Modifying Scanning Parameters, page 6-84.<br />

OL-25137-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!