Skip to main content

Message wasn't delivered because the recipient's email provider rejected it


  • Are there any other users who are experiencing the same issue?
  • As per the issue description it looks that the recipient is not accepting the mails from your domain or sender.
  • You can contact the recipient to check at their end.
  • Ask the recipient to Add your domain to their safe senders/Allowed/whitelist list. 



However below are the explanation for each of the possible scenarios.

Message wasn't delivered because the recipient's email provider rejected it

Means that the message was rejected by one of the servers trying to deliver it.

The Diagnostic information for administrators section may contain the following errors:

550 5.7.0 Proxy session setup failed on Frontend with '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domainIt may be caused by the following issues:
  • the recipient domain doesn't exist. Check the spelling of the domain and if public DNS (A and MX) records exist
  • the sending server is unable to resolve the DNS records of the domain. If you can look up the DNS records of the recipient domain from your own machine, contact Support

554 5.7.0 Reject id=xxxxx - SPAM

All messages sent to large mail providers (e.g. gmail.com, yahoo.com, etc.) are scanned when leaving our system in order to prevent spam from being sent using our servers. This error message indicates that the message was filitered and rejected as it got a very high spam score.
If the message was legitimate, contact Support and provide them with the full bounce back message (including the Diagnostic infotmaion for administrators section)
Note: the same error message may show up in the case of the following non-delivery report:
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator

5.7.0 x-unix; maildrop: maildir over quota

It indicates that the recipient POP mailbox has reached storage limits.
To resolve the issue:
  • delete or archive some of tha data in the mailbox
  • or increase the Receive limit on the Users & Services > POP/IMAP Mailboxes > username > Storage management page:

550 5.7.3 Message classification was not recognized ##rfc822

The error message indicates that Exchange server was unable to recognized message classification. If you're not using any custom classification, that usually means that the message is somehow corrupted and there is something in the message content that is preventing delivery.

To resolve the issue, copy and paste the text of the email to a new message. Should that not work, contact Support

Comments

Post a Comment

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...
Post a Comment
Read more

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...
4 comments
Read more

Block users from saving data on System Drive on Intune Managed Device

Recently i delivered a project for Intune Deployment and came up with a requirement as follows End Users Should not be able to save data locally on C or D Drive, instead they should be allowed to save data only in One Drive for business (synced with System)  Based on the requirement i did my research and found the Following. its possible to control the Local System settings on a Azure AD joined Machine and Managed by Intune. There is no options to define exceptions in policies to allow data saving in certain folders.  Now most of us will think WIP (windows information protection) policy will help us protecting the data on device, however that's not completely true as . User can change the File Ownership to personal if the WIP policy is set to Allow Override. User can save the file locally on the system User will not be able to copy the data from work file to Personal file if policy is set to Allow override. Unenlightened apps cannot differentiate between personal and corporate...
Post a Comment
Read more