Critical ErrorSMTP Error · Permanent (5.x.x)
554 5.4.14

Routing loop detected (Exchange Online)

A 554 5.4.14 from Exchange Online (5.4.6 from on-premises Exchange) means "Routing loop detected". The message kept going in a circle until Exchange stopped it.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 554 5.4.14 Routing loop detected (Exchange Online)
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

554 5.4.14 is a permanent SMTP reply meaning routing loop detected (exchange online). Microsoft explains that by default Exchange stops a mail loop after 20 iterations and sends a bounce. Loops usually come from a configuration error, such as forwarding or connectors that send mail back to where it came from.

What 554 5.4.14 means

Microsoft explains that by default Exchange stops a mail loop after 20 iterations and sends a bounce. Loops usually come from a configuration error, such as forwarding or connectors that send mail back to where it came from.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

Forwarding between two mailboxes or systems

Most common

Mailbox A forwards to B, and B forwards back to A.

🔁
#2

Hybrid or connector routing points back to itself

Common

An outbound connector or MX setting sends mail to the system that just sent it.

⚙️
#3

The domain is set up wrongly in Microsoft 365

Common

The domain is Authoritative in one system and Internal Relay in another, or MX points to the wrong place.

How to fix 554 5.4.14

  1. 1

    Read the hops in the bounce

    The headers in the bounce show which servers the message passed. Find the two that send it back and forth.

  2. 2

    Remove the loop

    Fix the forwarding rule, connector or accepted-domain setting that sends mail back.

  3. 3

    Check MX for the domain

    Run an MX lookup to confirm the domain points to the system that should receive its mail.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check