IronPort - advanced configuration guide

Chapter 2 Configuring Routing and Delivery Features
OL-25137-01
Figure 2-21 Global Unsubscribe Example
Review: Email Pipeline
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
IP interface: PublicNet (e.g. 192.168.2.1)
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:
A global unsubscribe entry for
the address user@example.net
was created. Messages to this
address will be bounced from
mail accepted by either private
or public listeners.
IronPort Email
Security appliance
Table 2-11 and Table 2-12 provide an overview of how email is routed through the system, from
reception to routing to deliver. Each feature is processed in order (from top to bottom) and is briefly
summarized. Shaded areas in Figure 2-21 represent processing that occurs in the Work Queue.
You can test most of the configurations of features in this pipeline using the trace command. For more
information, see “Debugging Mail Flow Using Test Messages: Trace” in the Cisco IronPort AsyncOS for
Email Daily Management Guide.
Cisco IronPort AsyncOS 7.6 for Email Advanced Configuration Guide
2-73