27.11.2012 Views

IronPort - Configuration Guide - AsyncOS 7.6.1

Create successful ePaper yourself

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

Chapter 5 Configuring the Gateway to Receive Email<br />

OL-25136-01<br />

Note You can also configure <strong>AsyncOS</strong> to perform this rejection at the message recipient level (RCPT<br />

TO), rather than at the start of the SMTP conversation. Rejecting messages in this way delays<br />

the message rejection and bounces the message, allowing <strong>AsyncOS</strong> to retain more detailed<br />

information about the rejected messages. This setting is configured from the CLI<br />

listenerconfig --> setup command. For more information, see “Customizing Listeners” in<br />

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

Step 3 TCPREFUSE<br />

Step 4 RELAY<br />

Connection is refused at the TCP level.<br />

Connection is accepted. Receiving for any recipient is allowed and is not constrained by the<br />

Recipient Access Table.<br />

CONTINUE<br />

The mapping in the HAT is ignored, and processing of the HAT continues. If the incoming<br />

connection matches a later entry that is not CONTINUE, that entry is used instead. The CONTINUE<br />

rule is used to facilitate the editing of the HAT in the Graphical User Interface (GUI). For more<br />

information, see Adding a New Sender Group, page 5-31.<br />

In addition to these basic access control parameters, the following parameters are available for listeners<br />

you create. Parameters combined with an access rule (ACCEPT or REJECT) are called mail flow<br />

policies. A mail flow policy is a way of expressing a group of HAT parameters (access rule, followed by<br />

connection parameters, rate limiting parameters, custom SMTP codes and responses, and anti-spam,<br />

anti-virus, encryption, and authentication parameters).<br />

Mail flow policies are then mapped to sender groups as entries in a listener’s HAT.<br />

Table 5-3 HAT Mail Flow Policy Parameters<br />

Parameter Description<br />

Connections<br />

Maximum message size The maximum size of a message that will be accepted by this listener.<br />

The smallest possible maximum message size is 1 kilobyte.<br />

Maximum concurrent<br />

connections from a single IP<br />

Maximum messages per<br />

connection<br />

Maximum recipients per<br />

message<br />

SMTP Banner<br />

The maximum number of concurrent connections allowed to connect to<br />

this listener from a single IP address.<br />

The maximum number of messages that can be sent through this listener<br />

per connection from a remote host.<br />

That maximum number of recipients per message that will be accepted<br />

from this host.<br />

Custom SMTP Banner Code The SMTP code returned when a connection is established with this<br />

listener.<br />

Custom SMTP Banner Text The SMTP banner text returned when a connection is established with<br />

this listener.<br />

Custom SMTP Reject Banner The SMTP code returned when a connection is rejected by this listener.<br />

Code<br />

Custom SMTP Reject Banner<br />

Text<br />

The SMTP banner text returned when a connection is rejected by this<br />

listener.<br />

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

5-9

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

Saved successfully!

Ooh no, something went wrong!