Advertisement
Guest User

Untitled

a guest
Apr 17th, 2017
915
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.33 KB | None | 0 0
  1. Your message to brian@xnergycapital.com couldn't be delivered.
  2. brian wasn't found at xnergycapital.com.
  3. brian Office 365 brian
  4. Action Required Recipient
  5. Unknown To address
  6.  
  7. How to Fix It
  8. The address may be misspelled or may not exist. Try one or more of the following:
  9. 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.
  10. Contact the recipient (by phone, for example) to check that the address exists and is correct.
  11. 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.
  12. 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.10 in Office 365, and then send the message again. Retype the entire recipient address before selecting Send.
  13. If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
  14.  
  15. Was this helpful? Send feedback to Microsoft.
  16.  
  17. More Info for Email Admins
  18. Status code: 550 5.1.10
  19.  
  20. This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. 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:
  21.  
  22. The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
  23.  
  24. 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.
  25.  
  26. Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
  27.  
  28. Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
  29.  
  30. Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings 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.
  31.  
  32. For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
  33.  
  34. Original Message Details
  35. Created Date: 4/17/2017 6:17:37 PM
  36. Sender Address: brian@xnergy.co
  37. Recipient Address: brian@xnergycapital.com
  38. Subject: Email Issue
  39.  
  40. Error Details
  41. Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
  42. DSN generated by: CY4PR08MB2647.namprd08.prod.outlook.com
  43. Message Hops
  44. HOP TIME (UTC) FROM TO WITH RELAY TIME
  45. 1 4/17/2017
  46. 6:17:37 PM CY4PR08MB2648.namprd08.prod.outlook.com CY4PR08MB2648.namprd08.prod.outlook.com mapi *
  47. 2 4/17/2017
  48. 6:17:37 PM CY4PR08MB2648.namprd08.prod.outlook.com CY4PR08MB2647.namprd08.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) *
  49. Original Message Headers
  50. Authentication-Results: xnergycapital.com; dkim=none (message not signed)
  51. header.d=none;xnergycapital.com; dmarc=none action=none
  52. header.from=xnergy.co;
  53. Received: from CY4PR08MB2648.namprd08.prod.outlook.com (10.172.157.147) by
  54. CY4PR08MB2647.namprd08.prod.outlook.com (10.172.157.146) with Microsoft SMTP
  55. Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
  56. 15.1.1034.10; Mon, 17 Apr 2017 18:17:37 +0000
  57. Received: from CY4PR08MB2648.namprd08.prod.outlook.com ([10.172.157.147]) by
  58. CY4PR08MB2648.namprd08.prod.outlook.com ([10.172.157.147]) with mapi id
  59. 15.01.1034.011; Mon, 17 Apr 2017 18:17:37 +0000
  60. Content-Type: application/ms-tnef; name="winmail.dat"
  61. Content-Transfer-Encoding: binary
  62. From: Brian Dean <brian@xnergy.co>
  63. To: "brian@xnergycapital.com" <brian@xnergycapital.com>
  64. Subject: Email Issue
  65. Thread-Topic: Email Issue
  66. Thread-Index: AQHSt6bka436rhYExkG5Eqa7dn7jbw==
  67. Date: Mon, 17 Apr 2017 18:17:37 +0000
  68. Message-ID: <CY4PR08MB2648D1E42E41A77ED9FB22E7B1060@CY4PR08MB2648.namprd08.prod.outlook.com>
  69. Accept-Language: en-US
  70. Content-Language: en-US
  71. X-MS-Has-Attach:
  72. X-MS-TNEF-Correlator: <CY4PR08MB2648D1E42E41A77ED9FB22E7B1060@CY4PR08MB2648.namprd08.prod.outlook.com>
  73. MIME-Version: 1.0
  74. X-Originating-IP: [73.157.237.85]
  75. X-Microsoft-Exchange-Diagnostics: 1;CY4PR08MB2648;35:8ENUHnLjh/eZJGhIKo5dS+NzjlXFryk7Wj2OOz8UBrCV/KLCtv1hdROq35OCBc6R/yT3LS+zfYFkxLwWr+9PXQ==
  76. Return-Path: brian@xnergy.co
  77. X-MS-Office365-Filtering-Correlation-Id: b9c18d91-41e3-4684-59e2-08d485be0700
  78. X-Microsoft-Antispam:
  79. UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254075)(201703131423075);SRVR:CY4PR08MB2647;
  80. X-Microsoft-Exchange-Diagnostics:
  81. 1;CY4PR08MB2647;3:L6Z/HuW8u+EgDE7W9qQeRb5EUJJdBnfnNLC5QFwBb0g36svtW2a8yUnkknVFpSyWPPN7QiSQeqmK2GqLDbOupxp0eaRzsUJG8n8RgI6oL4zjfy+kWLHrJuiQk7SEaE+5NIKWbq0vNXwltonTx54chnsBOk1FSxuj2QdqslL1YtV8zBeaeeLdFBkAEfdVxlNxDgldtXGKMkIsde74Ak+kAho6Edz+olGwOL60vWIHZ+VpIFbTz3MVcGdNzEDBiW/KW9k+9+6oCgv7hKjaSnwJ66PRkicnCQthyK9m2eDpchdvpc+HsMDBObqIXKNhM7gcbuf92hOMVSUL/NA8EpQuaQ==;25:MeqXZ0uXSj9Ly0muzmSHbyuefthbVbZe+lvlikjl9WgWM7jPWK5yJDl4i3lXiyhJyTsSgZU9DBSiR46aPZ2NxOR4ZFwfc7jrdapeNWygLDLiBUSM4ZWCZMxrHOBkzl3yPRvkIoZxujuJvBBDJSGax7hTXjmv8enrDMFtuNPyHY4hBcHnbVS6WXAauYhCEUOVSHlT0DOZJ8xwvHTwDCyEdMC/IBHnZUd4ULXrdBOnu2YI6ugbNharxdJzVCY0zhvrgsClDa1MptlhDzYh5qEO8ZKqklP0R5ayzQjb3kUAp8ikXsrAeAMlj3LAisejuCKIFNWZu9ZeBzSLqWozkLm/B3idMxPIDAp6X2xXGK2ysu/0LnM0m6rTkJnCun0R8KZM8/DWXU1ZDQrHoCnKm6Hji4PX8HKMe3DqEEkqfliyYP6yr27LH5buj13bgUW0VfANaa8xtuNJzwDAXxiQAxBAyg==
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement