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.

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

Too Many Recipients Bounce Filter<br />

OL-25137-01<br />

Bounce all outbound email messages with more than 50 recipients from more than two unique domains:<br />

Routing and Domain Spoofing<br />

Using Virtual Gateways Filter<br />

}<br />

insert-header ('X-HAT', 'Sender Group $Group, Policy $Policy applied.');<br />

bounce_high_rcpt_count:<br />

if ( (rcpt-count > 49) AND (rcpt-to != "@example\\.com$") ) {<br />

}<br />

bounce-profile ("too_many_rcpt_bounce"); bounce ();<br />

Segment traffic using virtual gateways. Assuming you have two Interfaces on the system, 'public1' and<br />

'public2', and the default delivery interface is 'public1'. This would force all of your outbound traffic over<br />

the second interface; since bounces and other similar types of mail do not go through filters, they will<br />

be delivered from public1:<br />

virtual_gateways:<br />

if (recv-listener == "OutboundMail") {<br />

}<br />

alt-src-host ("public2");<br />

Same Listener for Deliver and Injection Filter<br />

Use the same listener for delivery and receiving. This filter will allow you to send any messages received<br />

on the public listener “listener1” out the interface “listener1” (you will have to set up a unique filter for<br />

each public injector configured):<br />

same_listener:<br />

if (recv-inj == 'listener1') {<br />

}<br />

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

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

6-101

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

Saved successfully!

Ooh no, something went wrong!