IronPort - advanced configuration guide

Chapter 2 Configuring Routing and Delivery Features
OL-25137-01
Figure 2-6 Domain Map Defined for a Public Listener
Directing Bounced Email
Public Listener: InboundMail
Host Access Table (HAT):
WHITELIST: $TRUSTED
BLACKLIST: $BLOCKED
SUSPECTLIST: $THROTTLED
UNKNOWNLIST: $ACCEPTED
spamdomain.com REJECT
.spamdomain.com REJECT
251.192.1. TCPREFUSE
169.254.10.10 RELAY
ALL: $ACCEPTED
Recipient Access Table (RAT):
example.com ACCEPT
newcompanyname.com ACCEPT
ALL REJECT
Domain Map: enabled
IP interface: PublicNet (e.g. 192.168.2.1)
@.oldcompanyname.com
Ethernet interface: Data 2
Ethernet interface: Data 1
IP interface: PrivateNet (e.g. 192.168.1.1)
Private Listener: OutboundMail
Host Access Table (HAT):
RELAYLIST: $RELAYED
ALL: $BLOCKED
Default sender domain: example.com
Received: header: DISABLED
Masquerading:
@.example.com @example.com
A domain map for the public listener
“InboundMail” was created. Mail for
the domain and any subdomain of
oldcompanyname.com is mapped to
the domain example.com.
IronPort Email
Security appliance
Bounced email is an inevitable part of any email delivery. Your Cisco IronPort appliance is able to
process bounced email in a number of highly configurable ways.
Please note, this section describes how to control how your Cisco IronPort appliance generates outgoing
bounces (based on incoming mail). To control how your Cisco IronPort appliance controls incoming
bounces (based on outgoing mail) use Cisco IronPort Bounce Verification (see Cisco IronPort Bounce
Verification, page 2-53).
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
2-35