cancel
Showing results for 
Search instead for 
Did you mean: 

Office365 not receiving emails from email systems from outside Microsoft Hosted systems.

jac_95
Member

Hi all,

 

I have Business Essentials, which allows me to create upto so many email accounts using Office365 with the domain (in the format of domainP1-domainP2.org.uk) for free. This came when I purchased a domain from BT Business.

 

I'm able to send emails fine, however it seems that only users who use one of Microsofts email systems (eg Outlook or Office365) can only reach my email address eg info@domainP1-domainP2.org.uk.

 

Other email providers who don't use a Microsoft hosted system to route their emails, can't seem to reach one of my domain address.

 

It only effects the email accounts that use my domain, domainP1-domainP2.org.uk. btconnect.com account is not effected.

 

Some of the bounce back replies I get are below:

 

Technical details of temporary failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain domainP1-domainP2.org.uk by domainP1-domainP2-org-uk.mail.protection.outlook.com. [207.46.163.215].

The error that the other server returned was:
451 Temporary local problem - please retry later

 

AND:

Technical details of temporary failure:
DNS Error: Address resolution of ms85753994.msv1.invalid. failed: Domain name not found

 

The DNS records are shown below:

 

Type Key Value Priority (MX)

CNAMEautodiscoverautodiscover.outlook.com 
CNAMEsipsipdir.online.lync.com 
CNAMElyncdiscoverwebdir.online.lync.com 
CNAMEmailMail.btconnect.com 
MX@domainP1-domainP2-org-uk.mail.protection.outlook.com1
TXTdomainP1-domainP2.org.ukgoogle-site-verification=YiOXqOO3H4_ZVBhmWD285YVmko_K_cVZ0Zd0unMoQ4g 
CNAMEez72xge3fcr4gv-zbotyjiuppafak.dv.googlehosted.com 
CNAMEwwwghs.googlehosted.com 
TXT@v=spf1 include:spf.protection.outlook.com -all 
MX@ms81404801.msv1.invalid50
MX@ms85753994.msv1.invalid50
A@74.125.133.121

 

1 ACCEPTED SOLUTION

Accepted Solutions

jac_95
Member

This is now fixed.

 

Solution was to change the mx record, due to using a domain with a hythen, from

MX@domainP1-domainP2-org-uk.mail.protection.outlook.com1

 

to:

MX@domainP1-domainP2-org-uk02i.mail.protection.outlook.com1

View solution in original post

1 REPLY 1

jac_95
Member

This is now fixed.

 

Solution was to change the mx record, due to using a domain with a hythen, from

MX@domainP1-domainP2-org-uk.mail.protection.outlook.com1

 

to:

MX@domainP1-domainP2-org-uk02i.mail.protection.outlook.com1