27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 2 Configuring Routing and Delivery Features<br />

OL-25137-01<br />

#<br />

# Similarly, email to fred@mx.example.com will be<br />

# delivered to joseph@example.com<br />

#<br />

# [ironport.com, .example.com]<br />

#<br />

# joe, fred: joseph@example.com<br />

#<br />

# In this example, email to partygoers will be sent to<br />

# three addresses:<br />

#<br />

# partygoers: wilma@example.com, fred@example.com, barney@example.com<br />

#<br />

# In this example, mail to help@example.com will be delivered to<br />

# customercare@otherhost.dom. Note that mail to help@ironport.com will<br />

# NOT be processed by the alias table because the domain context<br />

# overrides the previous domain context.<br />

#<br />

# [example.com]<br />

#<br />

# help: customercare@otherhost.dom<br />

#<br />

# In this example, mail to nobody@example.com is dropped.<br />

#<br />

# nobody@example.com: /dev/null<br />

#<br />

# "Chains" may be created, but they must end in an email address.<br />

# For example, email to "all" will be sent to 9 addresses:<br />

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

2-11

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

Saved successfully!

Ooh no, something went wrong!