To configure the routing path for forwarded mail:

1. From the AMS Admin Console, as a Super Admin user, click System Settings >> Email Routing.
2. The Forwarding of Inbound Email to Your Mail System section displays the current forwarding setting, which is either:

• Forward email using MX records for your email domains.
• Forward email via mail routing policies.

4. To change the routing, click the Edit under the current forwarding setting.
5. The Routing Policy table lists all the mail routing policies currently in use.
6. Click Edit beside the policy to change it, or click Create Mail Routing Policy to create a new policy. This loads the Inbound Mail Routing Policy page.
7. Enter, or edit, the Policy Name.
8. Check the Customer Domain(s) for which this policy will apply.

NOTE

Note that if a domain is in use by another mail routing policy (Current Policy column), checking the Include In This Policy box and submitting the form will reassign the domain to this policy.

9. The Next Hops section of the form defines the ordered list of mail servers that messages will be routed to. If this section is left blank, the MX Records will be used for next hops. To enter next hop hosts, enter a fully-qualified domain name in the text-entry field and click Add. The hostname appears in the Next Hops in priority order box above. Repeat to add all required hostnames. Click the Up or Down buttons to specify the order of the hops.

10. In the Next Hop Transport Layer Security box, the Use Opportunistic TLS option is checked by default, which means AMS delivers messages via TLS, unless the recipient is not capable of receiving messages via TLS, in which case, AMS delivers the messages via SMTP. Unchecking the Use Opportunistic TLS checkbox forces TLS to be used in all communication with hosts. If the message recipient is unable to receive email via TLS, the message may not be delivered to that recipient. Support suggests this checkbox remain checked for most efficient communication between hosts.
11. To periodically test communication with next hops or MX records, check the Enable Readiness Checks box. See Next Hops Readiness Check
12. Click Submit to save the changes.

The new setting appears in the Forwarding of Inbound Email to Your Mail System section.

If the target specified within the AMS Next Hop Routing section (see Routing Policies for Forwarded Mail) is not configured to accept email from the AMS Data Center (over port 25/SMTP) it is possible that critical emails may not be delivered.

Examples of potentially affected content includes:

• Mail sent from activated users to non-activated users during Email Continuity activations
• End-user welcome messages
• Password reset email confirmations
• Readiness Check Fault Notification Alerts to your AMS administrators
• Other Data Center initiated communications

Given how critical it is that the AMS Data Center be able to successfully communicate with the destination mail systems, a Readiness Check attempts to establish a connection at least once per day over port 25 to each destination mail system specified. If AMS is unable to establish a successful connection an error will be displayed within the Readiness Check section of the AMS Admin Console.

Readiness Check Next Hop Status

Click the Details... link to review the individual test results.

Readiness Check Next Hop Status

If Not Connected statuses are displayed, ensure that your firewall has been configured to always allow connection attempts sent over port 25 from your data-center-specific IP addresses.

Contact Support if further assistance is required.

To configure the path for outbound mail during an activation:

1. From the AMS Admin Console, as emsroot user or as a Super Admin user, click System Settings >> Email Routing.
2. The Sending Outbound Email to External Recipients During an Activation section displays the current setting.
3. Click Edit.
4. In the Routing Rules section, select either:

• According to MX record(s) (default)
• Via specific hosts - If you select this option, enter the host name in the text-entry field and click Add. The hostname appears in the Hosts in priority order field above. Repeat to add all required hostnames.

5. Click Submit. The new setting appears in the Outbound Email to External Recipients During an Activation section.

Checking the box, Reject mail (421) while inactive (do not store and forward), disables Store and Forward functionality.

If checked (disabled) no email will be accepted for your organization unless you activate Email Continuity. It causes the AMS MTAs to soft reject messages with a 421 error unless you perform a full activation.

Spammers often target the lower priority public MX records. Therefore, if the AMS MTAs are listed as a lowest priority public MX record for your organization, you may wish to check this option (disable store and forward) so that the AMS MTAs do not accept mail unless you have activated Email Continuity for your entire organization.

For customers who utilize a 3rd-party mail gateway, and/or who do not list the AMSEmail Continuity MTAs in their public DNS, it is generally not recommended that this option be checked. If you have a use case where you still want to disable store and forward in this configuration, please contact Support to discuss the possible impacts of this configuration change.

To disable Store and Forward

1. As emsroot user or a Super Admin user, click on System Settings >> Email Routing.
2. In the Enable/Disable Store and Forward section, check Reject mail (421) while inactive (do not store and forward),.
3. To save the updates, click Submit at the bottom of the page.

For AMS users who use a 3rd-party external archive support, this field provides the means of entering the target address of the external archive provider.

It is advised that you contact Support before enabling this functionality.

To enable 3rd-party external archive support

1. As emsroot user or a Super Admin user, click on System Settings >> Email Routing.
2. In the Enable/Disable 3rd Party External Archive Support section, check Enable 3rd party external archive support for active users. This brings up a text-entry field.



Enable/Disable 3rd Party External Archive Support

3. Enter the target address of your external archive.
4. Click Submit at the bottom of the page.