“Recipient Address Rejected: access denied” error messages are frequently accompanied by the error codes 541 and 550, according to user feedback. The issue occurs if you send an outbound email to an email address that does not exist.
The relay access prohibited issue can also be caused by DNS cache corruption, an anti-spam filter, and Directory-Based Edge Blocking (DBEB). Fortunately, we look into a variety of fixes. Let’s give it a whirl.
Fix 1. Correctly Address the Recipient
You should verify that the recipient’s email address is valid before attempting any additional options. It’s also important to verify that the recipient’s email address is still allowed through the mail gateway. To fix the “550 5.4 1 Recipient Address Rejected Access Denied” problem message, check to see if the recipient address you’re using is accurate.
Fix 2. Verify That All Public Folders Are Stored Locally
After configuring the email with Exclaimer Cloud via Microsoft 365, some users receive the “Recipient Address Rejected: Access Denied” problem. Directory-Based Edge Blocking is most likely to blame for this problem. Email addresses from outside the Azure Active Directory can be rejected.
- There are three possible solutions to the problem listed below:
- Insist on on-premises hosting for all public folders
- Disable Directory-Based Edge Blocking for public folders hosted in Exchange Online (not recommended).
- The Microsoft Azure Active Directory Connect screen is the first step.
- Select Exchange Mail Public Folder from the right-hand pane of the Optional Features menu on the left-hand side of the window.
- To save your changes, click on the Next button. Send the email again and check if it fixes the “550 permanent failure for one or more recipients” problem.
Fix 3. Make Certain Your Public Folders Are Hosted on Exchange Online
You must use the Main flow menu to create an exception list because the DBEB option is not yet supported for mail-enabled public folders stored in Exchange Online. To ensure that your public files are hosted on Exchange Online, take these steps:
- Signing in to Exchange Online is the first step.
- Go to the Main flow area and select the Rules tab once you’ve logged in.
- Next, select the rule to transmit to Exclaimer Cloud: Identify Messages to Send. Scroll to the bottom of the page and click on Add Exception at the bottom of the page.
- From the Use the following connector section, choose The recipient…is this person.
- Select any public folder mailboxes that you use and click on Add to enforce the change, and then click on OK to execute it.
If the “550 5.4 1 Recipient Address Rejected access refused” issue is gone, try sending the email again.
Fix 4. Disable the Directory-Based Edge Blocking .
Disabling the DBED option is another way to stop it from preventing your emails from being delivered. This strategy can be used if the first two suggestions don’t work.
- Once you’ve logged back into Exchange Online, click on the Accepted Domains tab in the mail flow section.
- Next, select the public folder root domain and click Edit.
- In the This accepted domain is section, select the Internal relay domain option and then click on Save to turn off DBEB.
Check to see if the “relay access denied” problem is gone after this.
Fix 5: Reset DNS and TCP/IP Settings.
The “Recipient Address Rejected: Access Denied” problem might be caused by a poor DNS cache or a network device malfunction. A DNS and TCP/IP reset may help you resolve the issue.
Using the Search box, type cmd and then right-click Command Prompt and select Run as Administrator. Then, when prompted by the UAC window, select Yes.
Type the following commands one at a time into an elevated Command Prompt window, pressing Enter after each one.
- the /flushdns command
- It is possible to use the command line to monitor the status of your network.
- reset all netsh int ip netsh int restart
- reset-winsock netsh
Sending the email to the same recipient a second time should yield the same results.