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 1 Customizing Listeners<br />

Enabling TLS on a Listener’s HAT<br />

Assigning a Certificate<br />

OL-25137-01<br />

You must enable TLS for any listeners where you require encryption. You may want to enable TLS on<br />

listeners facing the Internet (that is, public listeners), but not for listeners for internal systems (that is,<br />

private listeners). Or, you may want to enable encryption for all listeners.<br />

You can specify 3 different settings for TLS on a listener. See Table 3-19.<br />

Table 1-6 TLS Settings for a Listener<br />

TLS Setting Meaning<br />

1. No TLS is not allowed for incoming connections. No connections to the listener<br />

will require encrypted SMTP conversations. This is the default setting for all<br />

listeners you configure on the appliance.<br />

2. Preferred TLS is allowed for incoming connections to the listener from MTAs.<br />

3. Required TLS is allowed for incoming connections to the listener from MTAs, and until<br />

a STARTTLS command is received, the Cisco <strong>IronPort</strong> appliance responds with<br />

an error message to every command other than NOOP, EHLO, or QUIT. This<br />

behavior is specified by RFC 3207, which defines the SMTP Service Extension<br />

for Secure SMTP over Transport Layer Security. “Requiring” TLS means that<br />

email which the sender is not willing to encrypt with TLS will be refused by the<br />

Cisco <strong>IronPort</strong> appliance before it is sent, thereby preventing it from be<br />

transmitted in the clear.<br />

By default, neither private nor public listeners allow TLS connections. You must enable TLS in a<br />

listener’s HAT to enable TLS for either inbound (receiving) or outbound (sending) email. In addition, all<br />

default mail flow policy settings for private and public listeners have the tls setting set to “off.”<br />

You can assign a specific certificate for TLS connections to individual public listeners when creating a<br />

listener. For more information, see Creating Listeners, page 1-7.<br />

You can assign a certificate to an individual public or private listener for TLS connections using either<br />

the Network > Listeners page or the listenerconfig -> edit -> certificate command in the CLI.<br />

To assign a TLS certificate via the GUI, select the certificate you want in the Certificate section when<br />

creating or editing a listener and then submit and commit your changes.<br />

Figure 1-18 Selecting a Certificate for a Listener<br />

To assign a certificate to a listener via the CLI, follow these steps:<br />

Step 1 Use the listenerconfig -> edit command to choose a listener you want to configure.<br />

Step 2 Use the certificate command to see the available certificates.<br />

Step 3 Choose the certificate you want to assign to the listener when prompted.<br />

Step 4 When you are finished configuring the listener, issue the commit command to enable the change.<br />

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

1-27

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

Saved successfully!

Ooh no, something went wrong!