Forum Discussion
Your message wasn't delivered because the recipient's email provider rejected it
Dear all, Recently, I registered 1 account Office 365 trial to experience O365 E3 version before bought it, I create a sharepoint site, upload some document and share with somebody, both the same...
No solution, happens about every other day, MS does not seem to care. Curious, do you have a paid version of Outlook365 (subscription). They are pushing that at $99/year. I already paid $400 for MS Office, so thought I didn't need this.
I'm having the same issue trying to send to an att.com email account. My email is one I've been using for 10+ years, so not new. Here's the text I get in the email failure notice:
XXXXXX@att.com (who I'm sending the email to)
Your message couldn't be delivered because the recipient's email server (outside of Office 365) rejected it because it couldn't determine if your message is coming from a location that is associated with your email domain. This is a security measure commonly done to help prevent malicious email or spam email from entering the recipient's email system. The reason the lookup failed is likely because your domain's email settings aren't set up correctly. To fix this, forward this non-delivery report (NDR) to your email admin.
For Email Admins
When Office 365 tried to send the message to the recipient's email server (outside Office 365), the external email server returned the error below. This means that when the recipient's email server was asked to accept the sender's message the server likely performed a reverse DNS (rDNS) lookup and the lookup failed. An email server outside Office 365 may perform an rDNS lookup to validate that the IP address the message is coming from is associated with your domain. The failed rDNS lookup suggests that the PTR record (pointer DNS record type) for your domain isn't set up properly.
To fix this, work with your DNS hosting provider (your domain registrar, Web hosting provider, or ISP) to set up a correct PTR record for your domain. If you're using Office 365 to manage your DNS records note that PTR record creation and management isn't supported by the Office 365 interface, in which case you'll have to change your DNS management to a DNS host outside Office 365. Refer to this article for instructions on how to do this:Change how DNS records are managed with Office 365.
Setting up PTR records is not supported by Office 365. Office 365 support will not be able to help you fix this problem.
XXXXXX@att.com (who I'm sending the email to)
Your message couldn't be delivered because the recipient's email server (outside of Office 365) rejected it because it couldn't determine if your message is coming from a location that is associated with your email domain. This is a security measure commonly done to help prevent malicious email or spam email from entering the recipient's email system. The reason the lookup failed is likely because your domain's email settings aren't set up correctly. To fix this, forward this non-delivery report (NDR) to your email admin.
For Email Admins
When Office 365 tried to send the message to the recipient's email server (outside Office 365), the external email server returned the error below. This means that when the recipient's email server was asked to accept the sender's message the server likely performed a reverse DNS (rDNS) lookup and the lookup failed. An email server outside Office 365 may perform an rDNS lookup to validate that the IP address the message is coming from is associated with your domain. The failed rDNS lookup suggests that the PTR record (pointer DNS record type) for your domain isn't set up properly.
To fix this, work with your DNS hosting provider (your domain registrar, Web hosting provider, or ISP) to set up a correct PTR record for your domain. If you're using Office 365 to manage your DNS records note that PTR record creation and management isn't supported by the Office 365 interface, in which case you'll have to change your DNS management to a DNS host outside Office 365. Refer to this article for instructions on how to do this:Change how DNS records are managed with Office 365.
Setting up PTR records is not supported by Office 365. Office 365 support will not be able to help you fix this problem.
