The Mimecast Gateway is a cloud based service that provides available services to your organization. Emails are routed from your organization to Mimecast for outbound delivery, and MX records are pointed to Mimecast for inbound delivery. The implementation of the Gateway for your organization is typically completed during the Mimecast Connect process.
Using the Mimecast Gateway
To route your organization’s email via the Mimecast Gateway, you need to update your SMTP Send Connectors for outbound mail and journaling, and also your MX records for inbound mail flow.
It is important to ensure that you allow connections to the appropriate ports from the entire Mimecast regional IP Ranges, and that they are mapped through to the correct destination on your network.
Update your organization’s send connectors and journal connectors (if applicable), using the hostnames as shown in the tables below.
Outbound Send Connectors
Standard accounts are for customers using on-premise, cloud or hosted email services. If you are using Microsoft Office 365, Mimecast provides dedicated hostnames as shown in the table below.
|Region||Standard Account Hostnames||Office 365 Account Hostnames|
Journaling Send Connectors
Please ensure that you have a dedicated Send Connector for SMTP Journal traffic configured. If your environment does not allow you to specify a dedicated Send Connector for SMTP Journal traffic you should use the Send Connector address as specified in the table above.
Update your organization's Zone File MX Records, using the appropriate entries from the table below. The hostnames should be added with the same priority to ensure round robining and failover.
|MX records (inbound)||Europe|
We recommend a preference/cost of 10 for both entries, but a different value may be chosen as long as both Mimecast entries are equal.