Chapter 20 Delivery Manager : Setting up Delivery Manager

Setting up Delivery Manager
Authorized administrators can configure/edit Delivery Manager. Exercise caution whenever making changes, as errors may impact your mail flow.
The Delivery Manager Edit page is shown below. Changes made to this page take effect with the next new mail server connection to the message security service.
Edit Delivery Manager
To navigate to the Delivery Manager edit screen, follow the steps below:
1.
2.
3.
4.
5.
6.
Email Servers and Load Balancing
Following are descriptions of the fields for Delivery Manager:
Use Google Apps Gmail
Send mail to Google Apps Gmail. This will send mail directly to Google Apps. Set up your domain in users in Google Apps as well as the message security server.
List your email server(s). Use either the mail host names (i.e. mail.sample.com) or the IP addresses (255.255.255.255). Either are acceptable formats.
If more fields are required, enter the first two and click Submit. After returning to the page, you will find additional fields. Repeat as necessary until all email hosts are listed.
Once you enter the mail host name or IP address and click Submit, the change occurs immediately! A faulty entry will prevent email from being delivered to your servers, thus stopping email from coming into your organization.
Important: You should test the email server after making any changes. You can test by validating that your email server is indeed receiving email from the message security service. Please contact support if you experience difficulty.
We recommend listing the email servers in descending order, with the most robust email server listed first. This will make it easier for calculating the distribution percentages for each email server.
Once all mail hosts are listed and connection limits are set, you can apply a weighted distribution of traffic across the servers. Enter the percentage allocation for each email server. For example, if you have three email servers and you want the first email server listed to receive 50% of the inbound email traffic, enter 50 in the % Connections field. Leaving the remaining fields empty will distribute the inbound messages equally among the remaining servers. Assigning a distribution percentage for each email server is fine as long as it totals 100. You will receive an error if you assign a load distribution that totals more than 100 percent. Also, only whole percentages may be used.
If you know how many simultaneous connections your email server can accommodate, set that value in the designated field. Submit the page and return. You will find that the number of open connections will be is displayed in bold- this is the real time number of open connections. This is useful to validate that you haven't set your Connection Limit too low. When an email server is experiencing an enormous amount of traffic, and the email server attempts to open enough connections to keep up with the requests, it can dramatically increase the likelihood of a server outage. Setting the Connection Limit in Delivery Manager will let the message security service act as an “edge server”, preventing your server from being overwhelmed and possibly brought down.
If you don't know your mail server connection limitations, we suggest you go to the “Host-specific data” available from the Delivery Manager-View page. If you configured your mail host properly, this will show the number of real time connections. Refresh the page several times over a few minutes to see how the number of connections fluctuates. Once you have an idea of the numerical range for open connections, set a limit that won't be too low to inhibit traffic, but isn't too high to allow your server to be disabled by excessive traffic. The email server software manual may also provide this information.
Connection limits are instituted starting with the first new connection created after the limit is set. The limit is not imposed on existing connection when the configuration is made. So connections will slowly settle down to the limit as existing connections to the server complete.
Fail over
Following are descriptions of field names for the fail over configuration.
A fail over email server is one that is kept out of regular rotation for inbound email traffic. The fail over server is designated to enter the email rotation if ALL of the primary email hosts fails. Like the primary email server, it too can be set with a connection limit and even receive a percentage of email traffic. When all primary email servers fail and there isn't a designated fail over server, the email will either be spooled by the message security service (if you have Spool Manager available) or the messages will be deferred.
Enter the host name or IP addresses of the mail servers that will be used in all primary email servers fail. See Email Servers and Load Balancing for more information.
The fail over configuration is one load-balanced set of servers, and not three full fail overs which fail over for each other in sequence.
Overflow
Click the check box if you wish to allow fail over email servers to accept excess messages beyond primary connection limits.
Dual Delivery Server
Following are descriptions of field names for the Dual Delivery configuration.
Enable Dual Delivery
Check to enable dual delivery. If checked, a message will be delivered to a dual delivery server if the message was successfully delivered to a registered user.
Send a copy to Google Apps Gmail
Send copy to this email server
 
*
*
*
*
*
*
*
*