Once your Mimecast account has been created, your Technical Point of Contact (TPOC) should log onto the account to confirm they can access it. If this is successful, your email server can be configured to route outbound emails through Mimecast. This requires that your:
- Public IP addresses are added to Mimecast's authorized outbounds. The Connect Team will configure these based on the information received in the Request for Information (RFI).
- Firewall is configured to allow access to Mimecast Data Center IP Ranges for SMTP port 25. See the Global Data Centers page for more information.
This step may not be applicable on Hosted Exchange (HEX) and Office 365 implementations. See the relevant section below for further detail.
- Email server or cloud service must be configured to deliver emails to Mimecast. See the relevant section below to display the configuration steps.
If you currently use SPF records for your domains, ensure you include a comprehensive list of Mimecast outbound IP addresses in your DNS SPF record. For more information, see the "Implementing SPF for Outbound Email Delivery" section of the DNS Authentication: Outbound Signing page.
Office 365 Environments
For detailed instructions, see the Office 365: Configuring Outbound Delivery Routing page.
On Premises Environments
Routing your outbound mail to Mimecast in Exchange is accomplished through the creation of a send connector. We provide two unique smarthosts per region to ensure 100% availability. We will email these to your Technical Point of Contact as part the Connect Process. The Mimecast Gateway page also provides this information. Both hostnames should be used to ensure round robin traffic as well as provide a failover.
For more information on how to configure SMTP connectors, view the relevant article below:
- Exchange 2013: Setting up an SMTP Connector
- Set up an SMTP Connector: Exchange 2010
- Set up an SMTP Connector: Exchange 2007
- Set up an SMTP Connector: Exchange 2003
- Lotus Domino: Setting up an SMTP Connector
If you utilize non-static public IP addresses, refer to the Configure SMTP Authentication on Exchange page.
You can monitor your live outbound traffic being logged by clicking the Administration | Gateway | Accepted Email menu item in the Administration Console. This displays all emails being processed by Mimecast.
Hosted Exchange (HEX) Environments
To set up your outbound email, forward our outbound routing instructions to your HEX provider to make the required changes. Ensure they consider the following when setting up your outbound email:
- In a multi-tenanted HEX environment, there are normally a number of customers on one server sending email outbound via a single Exchange send connector. If one of the customers on the HEX platform implements Mimecast, their outbound email must be separated from the rest of the clients on that HEX platform. All outbound email should then be sent to Mimecast for delivery, as opposed to being sent to the internet using the standard Exchange send connector. This is called Sender Address Based Routing, which is not a standard Exchange function. To implement Sender Address Based Routing, either a third party tool or additional hardware is required to send outbound email directly to Mimecast.
G Suite Environments
To prepare your outbound G Suite hostname: