How to fix x500 address in on-premises exchange after the migration?

Suman Shrestha 0

We have hybrid exchange setup. After the migration, the new accounts created have different x500 address format which has caused issue using printer services.

The emails are bouncing back with error:

Remote server returned '554 5.4.1 <ML1PEPF00011309.mail.protection.outlook.com #5.4.1 smtp;550 5.4.1 Recipient address rejected: Access denied. [ML1PEPF00011309.ausprd01.prod.outlook.com 2024-06-05T01:29:56.833Z 08DC84E0261C2B13]>

No issue with the migrated user though.

1 answer

Noah Ma-MSFT 2,340 Reputation points Microsoft Vendor

2024-06-07T09:59:48.5+00:00
Hi @Suman Shrestha,

Thank you for posting to Microsoft Community.

Based on your description, I know there are an issue you got a 5.4.1 error when you send email via the account created after migrated.

The reason why the issue occurred usually is the email server don't accept email from the sender's domain or DNS misconfiguration.

Please check the status of the domain in the Exchange admin center (EAC) by following these steps:

In the Microsoft 365 admin center, click Admin > Exchange.

Click Mail flow > Accepted domains.

Verify that your domain is listed and verify the Domain Type value for the domain. Typically, the value should be Authoritative. However, if you have properly configured a shared domain, the value might be Internal Relay.

For more information, you could refer to Fix NDR error code 550 5.4.1 in Exchange Online - Exchange | Microsoft Learn.

Also, please ensure DBEB (Directory Based Edge Blocking) is disable for your domain.

Hope it helps and if there is anything else I could help with, please let me know.
Please sign in to rate this answer.
Suman Shrestha 0 Reputation points

2024-06-10T23:35:43.4166667+00:00

Hi,

Thank you for the information. I have attached the screenshot of my accepted domains.

I am not sure how to disable DBEB if it's needed to be.

Please advise.

Thanks.

Noah Ma-MSFT 2,340 Reputation points Microsoft Vendor

2024-06-11T07:53:03.7666667+00:00

Hi,

Please take care of your privacy, I will cover your personal information of the screenshot, thanks for understanding.

I want to share the following with you. You received this error message because of the Directory-Based Edge Blocking (DBEB) according to Microsoft document.

By default, the DBEB is enabled for your domains in Microsoft 365 and will reject external emails with addresses that are not present within the Azure Active Directory.

You can have them manually disable it for your domain as the steps.

Log into Exchange Online.

Navigate to Mail flow, then select Accepted domains.

Select the domain then click Edit

Under This accepted domain is select Internal relay to disable DBEB.

Click Save.

Also, please kindly check this official document from Microsoft for the detailed steps on how a user or Admin can fix this issue. Fix email delivery issues for error code 550 5.4.1 in Exchange Online | Microsoft Learn

Hope it could be any help to you.

Suman Shrestha 0 Reputation points

2024-06-11T22:45:17.01+00:00

Hi @Noah Ma-MSFT ,

Not really sure how the new email addresses are being detected as external emails? It works fine when sending emails using exchange online. We are having issues when those new mailboxes use on-prem services such scan-to-email in printers which uses our on-prem exchange. We have Hybrid exchange deployment in our site (school). Also, we don't have any 3rd party protection in front of 0365. Will it be alright to disable DBEB? Please advise.

Thanks.

Noah Ma-MSFT 2,340 Reputation points Microsoft Vendor

2024-06-13T09:47:17.32+00:00

Hi,

I want to confirm with you that if you mean you got 550 5.4.1 error message when you use the new on-premises mailbox.

If there is only one is affected, please check the users smtp email addresses are correct on the Exchange hybrid server.

Check if the user was missing the @DOMAIN.onmicrosoft.com smtp email address, and if the remote routing address was set correctly on the Exchange hybrid server as screenshot below.

Hope it helps and if there is anything else you need help with, please let me know.

Noah Ma-MSFT 2,340 Reputation points Microsoft Vendor

2024-06-18T10:05:41.8333333+00:00

Just checking in to see if above information was helpful.

If the issue has been resolved, please mark the helpful replies as answers.
Sign in to comment

Share via

How to fix x500 address in on-premises exchange after the migration?

1 answer