Mimecast Gateway

Document created by user.oxriBaJeN4 Employee on Sep 7, 2015Last modified by user.oxriBaJeN4 Employee on May 23, 2018
Version 11Show Document
  • View in full screen mode

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.

Send Connectors

 

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.

 

RegionStandard Account HostnamesOffice 365 Account Hostnames

Europe (Excluding Germany)

eu-smtp-outbound-1.mimecast.com

eu-smtp-outbound-2.mimecast.com

eu-smtp-o365-outbound-1.mimecast.com

eu-smtp-o365-outbound-2.mimecast.com

Germany

de-smtp-outbound-1.mimecast.com

de-smtp-outbound-2.mimecast.com

de-smtp-o365-outbound-1.mimecast.com

de-smtp-o365-outbound-2.mimecast.com

America

us-smtp-outbound-1.mimecast.com

us-smtp-outbound-2.mimecast.com

us-smtp-o365-outbound-1.mimecast.com

us-smtp-o365-outbound-2.mimecast.com

South Africa

za-smtp-outbound-1.mimecast.co.za

za-smtp-outbound-2.mimecast.co.za

za-smtp-o365-outbound-1.mimecast.co.za

za-smtp-o365-outbound-2.mimecast.co.za

Australia

au-smtp-outbound-1.mimecast.com

au-smtp-outbound-2.mimecast.com

au-smtp-o365-outbound-1.mimecast.com

au-smtp-o365-outbound-2.mimecast.com

Offshore

je-smtp-outbound-1.mimecast-offshore.com

je-smtp-outbound-2.mimecast-offshore.com

je-smtp-o365-outbound-1.mimecast-offshore.com

je-smtp-o365-outbound-2.mimecast-offshore.com

 

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.

 

Region
Hostname
Europe (Excluding Germany)

eu-smtp-journal-1.mimecast.com

eu-smtp-journal-2.mimecast.com

Germany

de-smtp-journal-1.mimecast.com

de-smtp-journal-2.mimecast.com

North America

us-smtp-journal-1.mimecast.com

us-smtp-journal-2.mimecast.com

South Africa

za-smtp-journal-1.mimecast.co.za

za-smtp-journal-2.mimecast.co.za

Australia

au-smtp-journal-1.mimecast.com

au-smtp-journal-2.mimecast.com

Offshore

je-smtp-journal-1.mimecast-offshore.com

je-smtp-journal-2.mimecast-offshore.com

 

MX Records

 

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.

 

Function
Region
Hostname
MX records (inbound)Europe (Excluding Germany)

eu-smtp-inbound-1.mimecast.com

eu-smtp-inbound-2.mimecast.com

Germany

de-smtp-inbound-1.mimecast.com

de-smtp-inbound-2.mimecast.com

North America

us-smtp-inbound-1.mimecast.com

us-smtp-inbound-2.mimecast.com

South Africa

za-smtp-inbound-1.mimecast.co.za

za-smtp-inbound-2.mimecast.co.za

Australia

au-smtp-inbound-1.mimecast.com

au-smtp-inbound-2.mimecast.com

Offshore

je-smtp-inbound-1.mimecast-offshore.com

je-smtp-inbound-2.mimecast-offshore.com

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.

3 people found this helpful

Attachments

    Outcomes