Send & Receive Issues

Fix Microsoft 365 Email Forwarding Error 5.4.1 Recipient Not Found

WPS EditorWPS Editor Oct 9, 2026 868 views

Question details

Users need to resolve an issue where forwarded emails are rejected by the external recipient's email server.

Fix Microsoft 365 Email Forwarding Error 5.4.1 Recipient Not Found
Product
Microsoft 365
Device & OS
not provided
Scenario
Forwarding an email from an internal Microsoft 365 address to an external recipient whose organization utilizes FortiMail.
Observed behavior
The email fails to deliver, resulting in a bounce-back Non-Delivery Report (NDR) citing a 5.4.1 Recipient Not Found error.
Before you start

Verify the external recipient's email address for spelling errors and confirm with other senders if they are experiencing similar bounce-backs when emailing this specific address.

Solution 1Recommended

Contact the Recipient IT Administrator to Update FortiMail Directory

Since the error originates from the recipient's FortiMail server, their IT support team must fix the directory synchronization.

When an organization uses FortiMail with Directory-Based Edge Blocking (DBEB), their edge server checks incoming emails against a synchronized directory of valid email addresses. If an address has not synced correctly to the edge directory, the FortiMail server will actively reject the message with a 5.4.1 error, even if the mailbox exists on their internal mail server.

1
Identify the failing recipient address

Review the Non-Delivery Report (NDR) email you received to identify the exact external email address that is returning the 5.4.1 error.

2
Reach out via alternative methods

Contact the external recipient or their organization's IT support desk via a phone call or an alternative messaging platform, as they will not receive your forwarded emails.

3
Request directory synchronization

Inform the recipient's IT administrator that their FortiMail edge server is returning a '5.4.1 Recipient Not Found' error and ask them to verify the mailbox status and manually trigger a directory synchronization.

Contact the Recipient IT Administrator to Update FortiMail Directory
Resolution Propagation Time: After the recipient's administrator updates the FortiMail directory, it may take up to a few hours for the synchronization to propagate fully across their edge servers before you can successfully forward emails to them.
Free Microsoft Office alternative

Looking for a Lightweight Alternative to Microsoft 365?

While email server routing issues require IT intervention, your daily document management shouldn't be complicated. If you are exploring cost-effective alternatives to Microsoft 365, WPS Office provides a free, highly compatible, and user-friendly suite for all your document, spreadsheet, and presentation needs.

  1. 1. Download the software: Visit the official WPS Office website and download the installation package suited for your operating system.
  2. 2. Install WPS Office: Run the installer. The lightweight package installs quickly without consuming heavy system resources.
  3. 3. Open your existing files: Launch WPS Office and directly open your existing Microsoft Office documents seamlessly.
Free to download and use with a highly intuitive user interface similar to Microsoft Office.Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx) to prevent formatting loss.Lightweight installation that runs smoothly on Windows, Mac, iOS, Android, and Linux.Includes built-in advanced PDF editing, converting, and cloud collaboration tools without extra subscription fees.
microsoft office alternative - wps office

Frequently Asked Questions

What does the 5.4.1 Recipient Not Found error mean?

This error means that the receiving email server rejected the incoming message because it could not find the specified email address in its active directory. This is common with security gateways like FortiMail that use directory-based edge blocking.

Can I fix the 5.4.1 error from my Microsoft 365 admin center?

Generally, no. If the bounce-back report indicates that the recipient's server (such as a FortiMail server) generated the error, the fix must be applied on the recipient's side by their IT administrator, not within your Microsoft 365 settings.

Why did forwarding trigger this error when direct emails might not?

Forwarded emails can sometimes contain different sender headers or routing properties. Strict edge protection servers like FortiMail might scrutinize these forwarded messages more heavily and reject the recipient address if the directory synchronization is slightly out of date or misconfigured.