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.

Listeners Overview<br />

1-2<br />

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

Chapter 1 Customizing Listeners<br />

The Network > Listeners page and the listenerconfig command in the CLI allow you to create, edit,<br />

and delete a listener. Cisco <strong>IronPort</strong> AsyncOS requires that you specify criteria that messages must meet<br />

in order to be accepted and then relayed to recipient hosts — either internal to your network or to external<br />

recipients on the Internet.<br />

These qualifying criteria are defined in listeners; collectively, they ultimately define and enforce your<br />

mail flow policies. Listeners also define how the Cisco <strong>IronPort</strong> appliance communicates with the<br />

system that is injecting email.<br />

Each listener is composed of the criteria shown in Table 1-1.<br />

Table 1-1 Criteria for Listeners<br />

Name Unique nickname you supply for the listener, for future reference. The names you<br />

define for listeners are case-sensitive. AsyncOS will not allow you to create two<br />

identical listener names.<br />

IP interface Listeners are assigned to IP interfaces. The IP interface is defined by the<br />

interfaceconfig command. Any IP interfaces must be configured using the<br />

System Setup Wizard or the systemsetup command or the IP Interfaces page (or<br />

the interfaceconfig command) before you create and assign a listener to it. The<br />

version of the Internet Protocol address of the interface determines the type of<br />

traffic the listener accepts. If the IP interface has both an IPv4 and IPv6 address,<br />

then the listener can accept connections from both IPv4 and IPv6 addresses.<br />

Mail protocol The mail protocol to used for email receiving: either SMTP or QMQP (only<br />

available via the listenerconfig command in the CLI).<br />

IP port The specific IP port used for connections to the listener. By default, SMTP uses<br />

port 25 and QMQP uses port 628.<br />

Listener Type: Public Public and private listeners are used for most <strong>configuration</strong>s. By<br />

Private convention, private listeners are intended to be used for private<br />

(internal) networks, while public listeners contain default<br />

characteristics for receiving email from the Internet.<br />

Blackhole “Blackhole” listeners can be used for testing or troubleshooting<br />

purposes. When you create a blackhole listener, you choose whether<br />

messages are written to disk or not before they are deleted. (See<br />

“Testing and Troubleshooting” in the Cisco <strong>IronPort</strong> AsyncOS for<br />

Email Daily Management Guide for more information.) Writing<br />

messages to disk before deleting them can help you measure the rate<br />

of receiving and the speed of the queue. A listener that doesn’t write<br />

messages to disk can help you measure the pure rate of receiving<br />

from your message generation systems. This listener type is only<br />

available through the listenerconfig command in the CLI.<br />

In addition to these criteria, you can also configure the following for each listener:<br />

SMTP Address Parsing Options (optional settings for controlling parsing in SMTP “MAIL FROM”<br />

and “RCPT TO,” see SMTP Address Parsing Options, page 1-8)<br />

Advanced Configuration Options (optional settings for customizing the behavior of the Listener, see<br />

Advanced Configuration Options, page 1-11)<br />

LDAP Options (optional settings for controlling LDAP queries associated with this Listener, see<br />

LDAP Options, page 1-12)<br />

OL-25137-01

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

Saved successfully!

Ooh no, something went wrong!