The Mimecast Gateway is a cloud based service that provides available services to your organization. Messages are routed from your organization to Mimecast for outbound delivery, and MX records are pointed to us for inbound delivery. The gateway's implementation is typically completed via the Connect Application or Connect Process.
Using the Mimecast Gateway
To route your messages via the Mimecast Gateway, you must update your SMTP send connectors for outbound mail and journaling, and also your MX records for inbound mail flow.
You must allow connections to the appropriate ports from all Mimecast regional IP ranges, and ensure they're mapped through to the correct destination on your network. View the Mimecast Data Centers and URLs page for more information.
Update your organization’s send connectors and journal connectors (if applicable), using the hostnames displayed 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|
Europe (Excluding Germany)
Journaling Send Connectors
You must configure a dedicated send connector for SMTP journal traffic. If your environment doesn't allow this, use the send connector address as specified above.
|Europe (Excluding Germany)|
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 (Excluding Germany)|
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.