Hi all,
I seem to have hit upon an odd issue with 2 new domains I've setup within Mimecast. My other 13-ish domains are all running fine, but 2 new ones both exhibit the same issue.
If I try to send an email to the domain, in this case domain2.com which is hosted on O365, everything is setup identically to my other domains, but I get a bounce message of "4.4.62 Mail sent to the wrong Office 365 region" with a link to a MS page regarding the issue.
However, if I take Mimecast out of the equation and route the email directly to MS (so change MX records and connector details in O365), the email goes there without issue. However, if I change it to run through Mimecast, I keep getting that error everytime. Microsoft have looked into it thoroughly and claim that because it runs without issue if Mimecast is not in the equation, then it proves there is no issue with their setup, which seems logical. But I can't see how it is any different to any of my other domain setups.
Below is the full Strict-TLS test result. You can see it appears to resolve the IP to Microsoft happily, communicate with the MS server and then, at the very end, return that result.
Resolve hostname domain2-com.mail.protection.outlook.com:
104.47.21.36
Checking the IP address 104.47.21.36:
The IP address has a valid format.
The IP address is public.
Execute the SMTP connection test with the given parameters:
220 eu-smtp-1.mimecast.com ESMTP; Mon, 28 Jan 2019 19:42:43 +0000
MCCONNECT null domain2-com.mail.protection.outlook.com:25
220 CWLGBR01FT012.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Mon, 28 Jan 2019 19:42:43 +0000
EHLO eu-smtp-1.mimecast.com
250-CWLGBR01FT012.mail.protection.outlook.com Hello [195.130.217.76]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
STARTTLS
220 2.0.0 SMTP server ready
EHLO eu-smtp-1.mimecast.com
250-CWLGBR01FT012.mail.protection.outlook.com Hello [195.130.217.76]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
MAIL FROM:smtptest@mimecast.com
250 2.1.0 Sender OK
RCPT TO:john.doe@domain1.com
551 4.4.62 Mail sent to the wrong Office 365 region. ATTR35. For more information please go to https://go.microsoft.com/fwlink/?linkid=865268 [CWLGBR01FT012.eop-gbr01.prod.protection.outlook.com]
QUIT
An error occured.
Execute the SMTP connection test with the given parameters:
220 eu-smtp-1.mimecast.com ESMTP; Mon, 28 Jan 2019 19:42:43 +0000
MCCONNECT null domain2-com.mail.protection.outlook.com:25
220 CWLGBR01FT011.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Mon, 28 Jan 2019 19:42:42 +0000
EHLO eu-smtp-1.mimecast.com
250-CWLGBR01FT011.mail.protection.outlook.com Hello [91.220.42.220]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
STARTTLS
220 2.0.0 SMTP server ready
EHLO eu-smtp-1.mimecast.com
250-CWLGBR01FT011.mail.protection.outlook.com Hello [91.220.42.220]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
MAIL FROM:smtptest@mimecast.com
250 2.1.0 Sender OK
RCPT TO:john.doe@domain1.com
551 4.4.62 Mail sent to the wrong Office 365 region. ATTR35. For more information please go to https://go.microsoft.com/fwlink/?linkid=865268 [CWLGBR01FT011.eop-gbr01.prod.protection.outlook.com]
QUIT
An error occured.
Any suggestions or help gratefully received. Maybe I'm missing something (its possible I'm just too close and missing something really obvious), but I can't see it and I've successfully setup 13 other domains without issue.
Thanks
Bob
Hi Bob,
I've edited your post so that your email address and domains are generic, for privacy purposes.
I'm going to send you a private message regarding this, just to avoid sharing your personal email address on this thread. I believe the issue here is that the TO address being used in the test belongs to an email domain that this specific O365 tenant is not configured to accept mail for (your main email address is the TO address, but the O365 tenant you're sending to is for a different domain. Setting a specific Delivery Routing policy for the second domain should do the trick.
Thanks,
Corey