Delivery Routing Policies

Document created by user.oxriBaJeN4 Employee on Sep 11, 2015Last modified by user.oxriBaJeN4 Employee on Mar 27, 2017
Version 6Show Document
  • View in full screen mode

Delivery routes are used to deliver emails from Mimecast. Typically this is inbound email to your local infrastructure, although they can also be used to override MX records for outbound delivery. Delivery Routes contain the details of the delivery destination (e.g. the Host Name or IP Address of the email server). Mimecast’s flexible Routing Policies allow emails to be delivered to a specific server based on a domain, Group, Attribute or individual address.


Delivery routes determine the route to be used for inbound email delivery. By default, outbound emails will be delivered to the recipient using available MX records. However if an outbound delivery route has been configured, this would override the MX record. Delivery routes require the specific route to be configured, and a policy to determine the flow of traffic. Alternate routes can also be created, which enable a failover option, should a customer’s primary route be unavailable.


If multiple similar routes (the FROM and TO variables are the same) are configured, this will result in a round robin (random selection) of these routes. This is also useful to balance mail server load.

What you need

  • An Administrator Console logon with access to the Administration | Gateway | Policies menu item.
  • A previously configured Delivery Routing definition.


Creating a policy


To create a policy, follow the instructions in the Creating / Changing a Policy article, but using the following options:


Policy NarrativeProvide a description for the Policy to allow you to easily identify it in the future.
Select Route

Select a Delivery Routing definition for the policy.

Definition required?