27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 1 Customizing Listeners<br />

Partial Domains, Default Domains, and Malformed MAIL FROMs<br />

OL-25137-01<br />

Table 1-3 SMTP Address Parsing Additional Options<br />

Option Description Default<br />

%!:@<br />

Reject User Names<br />

containing These<br />

Characters:<br />

Unknown Address<br />

Literals (IPv6, etc.):<br />

reject, accept<br />

If you enable envelope sender verification or disable allowing partial domains in SMTP Address Parsing<br />

options for a listener, the default domain settings for that listener will no longer be used.<br />

These features are mutually exclusive.<br />

Advanced Configuration Options<br />

To access the Advanced options, expand the section by clicking on Advanced in the listing.<br />

Figure 1-7 Listeners Advanced Options<br />

Advanced <strong>configuration</strong> options include:<br />

Usernames that include characters (such as % or !, for example)<br />

entered here will be rejected.<br />

Determines behavior for when an address literal is received that<br />

the system can not handle. Currently, this is everything except for<br />

IPv4. Thus, for example, for an IPv6 address literal, you can<br />

either reject it at the protocol level, or accept it and immediately<br />

hard bounce it.<br />

Recipient addresses containing literals will cause an immediate<br />

hard bounce. Sender addresses may get delivered. If the message<br />

cannot be delivered, then the hard bounce will hard bounce<br />

(double hard bounce).<br />

In the case of reject, both sender and recipient addresses will be<br />

rejected immediately at the protocol level.<br />

Add Received Header: Add a received header to all received email. A listener also modifies email<br />

that it relays by adding a Received: header on each message. If you do not want to include the<br />

Received: header, you can disable it using this option.<br />

Note The Received: header is not added to the message within the work queue processing. Rather, it is added<br />

when the message is enqueued for delivery.<br />

Disabling the received header is a way to ensure that your network’s topology is not exposed by<br />

revealing the IP addresses or hostnames of internal servers on any messages travelling outside your<br />

infrastructure. Please use caution when disabling the received header.<br />

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

reject<br />

1-11

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

Saved successfully!

Ooh no, something went wrong!