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.

Default Delivery Limits<br />

2-46<br />

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

Chapter 2 Configuring Routing and Delivery Features<br />

Each outbound destination domain has its own outbound queue. Therefore, each domain has a separate<br />

set of concurrency limits as specified in the Destination Controls table. Further, each unique domain not<br />

listed specifically in the Destination Controls table uses another set of the “Default” limits as set in the<br />

table.<br />

Working with Destination Controls<br />

Use the Mail Policies > Destination Controls page in the GUI or the destconfig command in the CLI to<br />

create, edit, and delete Destination Control entries.<br />

Controlling the Version of Internet Protocol Addresses<br />

You can configure which version of Internet Protocol addresses to use for the connection to a domain.<br />

The Email Security appliance uses both Internet Protocol version 4 (IPv4) and Internet Protocol version<br />

(IPv6). You can configure a listener on the appliance to use one version of the protocol or both.<br />

If the “Required” setting for either IPv4 or IPv6 is specified, the Cisco <strong>IronPort</strong> appliance will negotation<br />

a connection to the domain using an address of the specified version. If the domain doesn’t use that IP<br />

address version, no email will be sent. If the “Preferred” setting for either IPv4 or IPv6 is specified, the<br />

Cisco <strong>IronPort</strong> appliance will first attempt to negotation a connection to the domain using an address of<br />

the specified version then fall back to the other if the first is not reachable.<br />

Controlling the Number of Connections, Messages, and Recipients to a Domain<br />

You may want to limit how your appliance will deliver email to avoid overwhelming remote hosts or your<br />

own internal groupware servers with email from your appliance.<br />

For each domain, you can assign a maximum number of connections, outbound messages, and recipients<br />

that will never be exceeded by the system in a given time period. This “good neighbor” table is defined<br />

through the Destination Controls feature (Mail Policies > Destination Controls or the destconfig<br />

command — previously the setgoodtable command). You can specify the domain name using the<br />

following syntax:<br />

domain.com<br />

or<br />

.domain.com<br />

This syntax enables AsyncOS to specify destination controls for sub-domains such as<br />

sample.server.domain.com without entering each full subdomain address individually.<br />

For connections, messages, and recipients, you set whether the limits you define are enforced for each<br />

Virtual Gateway address, or for the entire system. (Virtual Gateway address limits control the number of<br />

concurrent connections per IP interface. System-wide limits control the total number of connections the<br />

Cisco <strong>IronPort</strong> appliance will allow.)<br />

You also set whether the limits you define are enforced for each MX record of the specified domain, or<br />

for the entire domain. (Many domains have multiple MX records defined for accepting email.)<br />

Note The current system default is 500 connections per domain and 50 messages per connection.<br />

OL-25137-01

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

Saved successfully!

Ooh no, something went wrong!