Send & Receive Issues

Fix Microsoft 365 Email Forwarding Routing Loop Error 550 5.4.142

Camila MilosovichCamila Milosovich Oct 9, 2026 869 views

Question details

Users need to resolve a routing loop issue that prevents emails from being forwarded or redirected to another address within the same domain.

Fix Microsoft 365 Email Forwarding and Routing Loop Errors
Product
Microsoft 365
Device & OS
not provided
Scenario
Configuring email redirection or forwarding to another address in the same domain.
Observed behavior
Email delivery fails and bounces back with a 550 5.4.142 RESOLVER.FWD.LoopingTarget error, indicating a circular routing loop.
Before you start

Ensure you have Microsoft 365 administrator privileges, as modifying Exchange transport rules and running detailed message traces require elevated access.

Solution 1Recommended

Identify and Remove Circular Forwarding Rules

Check the forwarding configurations across mailboxes, contacts, and distribution groups to break the circular routing loop.

A routing loop occurs when an email is continuously forwarded back and forth between two or more addresses. To resolve the 550 5.4.142 error, you must identify where the circular reference is created and disable it.

1
Access the Exchange Admin Center

Log in to the Microsoft 365 admin center with your administrator credentials and navigate to the Exchange Admin Center.

2
Review Mailbox Forwarding Settings

Go to 'Recipients' and select 'Mailboxes'. Open the affected mailbox, click on the 'Mailbox' tab, and select 'Manage email forwarding'. Ensure the forwarding address does not route back to the original sender.

3
Check Distribution Group Members

Navigate to 'Recipients' > 'Groups'. Ensure that the forwarding address is not a member of a distribution group that also forwards emails back to the original mailbox.

4
Inspect Transport Rules

Go to 'Mail flow' > 'Rules'. Carefully review active transport rules to verify that there are no automated redirection conditions creating an infinite loop between internal domain addresses.

Identify and Remove Circular Forwarding Rules
Propagation Time: Changes made to forwarding addresses and transport rules in the Exchange Admin Center may take a few hours to fully propagate and resolve the bouncing issue.
Free Microsoft Office alternative

Need a Reliable and Lightweight Office Suite? Try WPS Office

While resolving complex Microsoft 365 server configurations can be tedious, managing your daily documents should be hassle-free. WPS Office is a lightweight, fully compatible, and free alternative to Microsoft Office that meets all your word processing, spreadsheet, and presentation needs.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install and Launch: Run the installer and follow the on-screen prompts. Once installed, open the application to access Writer, Spreadsheets, and Presentation.
  3. 3. Open Your Documents: Easily open your existing Microsoft Office files. WPS Office automatically recognizes the formats, allowing you to edit and save seamlessly.
Highly compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Lightweight design that runs smoothly on older devices without consuming heavy system resources.Features a built-in PDF reader and editor for easy all-in-one document management.Familiar tabbed user interface, ensuring a seamless transition and zero learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

What does the 550 5.4.142 RESOLVER.FWD.LoopingTarget error mean?

This error occurs when Microsoft 365 detects an email being forwarded in an infinite loop between addresses. To prevent server overload, Exchange automatically blocks the message and sends a Non-Delivery Report (NDR) containing this error code.

Can inbox rules set up by end-users cause routing loops?

Yes. If an end-user sets up an Outlook Inbox rule to automatically forward emails to a colleague, and that colleague has a similar rule forwarding emails back to the first user, it will trigger a routing loop error. Both users' inbox rules need to be checked.

How can I analyze bounced message headers to find the loop?

You can copy the message header from the Non-Delivery Report email and paste it into the Microsoft Remote Connectivity Analyzer (Message Analyzer tab). It will break down the routing hops, helping you see the exact path the email took before the loop was detected.