Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Your message to email address couldn't be delivered

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

Your message to email address couldn't be delivered

Postby blin » Wed Sep 28, 2016 5:49 pm

Situation: The client can't send email to another domain user with this message:
Your message to email address couldn't be delivered.
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365, and then send the message again. Retype the entire recipient address before selecting Send.


More Info for Email Admins
Status code 554 5.4.14

Typically this error occurs because the recipient email address is incorrect or doesn't exist at the destination domain. This can usually be fixed by the sender. However, sometimes the issue needs to be fixed by the recipient or the recipient's email admin. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. A forwarding rule can be configured by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Mail flow settings and MX records are not correct - Misconfigured mail flow settings or MX records can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

Mail loop detected - This error also indicates that the receiving organization's email settings are misconfigured, creating a mail loop when a message is sent to an address that isn't found in their directory. This usually won't disrupt mail flow for recipients that actually exist, but the recipient's email admin should fix the misconfiguration to reduce the chance of any other mail flow issues. A common cause for this loop is that the recipient's domain is configured as "Internal Relay" when it should be "Authoritative." Another common cause for the loop is that both the sender and recipient are part of the same organization, but the sender's mailbox is hosted by Office 365, while the recipient's mailbox is hosted on-premises, and an outbound connector from Office 365 to the on-premises email servers is missing or misconfigured. To fix this, the recipient's email admin should create a correctly configured outbound connector in Office 365 to route the message to the on-premises mailbox.

For more information and tips to fix this problem, see Fix email delivery issues for error code 5.4.14 in Office 365.

Original Message Details
Created Date: 9/28/2016 5:49:41 PM
Sender Address: blin@chicagotech.net

Recipient Address: info@chicagotech.net

Subject: test


Error Details
Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34
DSN generated by: SN1PR07MB1440.namprd07.prod.outlook.com
Remote server: CO1NAM03FT059.mail.protection.outlook.com

Troubleshooting: All internal users have this issue to send email to the same user. However, external users don't have the problem to send email to the user.
We find the user has a forwarding settings to forward all emails to a disable account. Removing the disable account from the forwarding fixes the problem.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3643
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Your message to email address couldn't be delivered

Postby chicagotech » Thu Feb 23, 2017 11:15 am

In our case, the user doesn't have Office 365 license. Adding E1 license fixes the problem.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7084
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Re: Your message to email address couldn't be delivered

Postby chicagotech » Thu Feb 23, 2017 11:15 am

In most cases, this is receipt email problem. Try to repair Outlook.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7084
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 7 guests