5.4.6 means the message went round in a loop — forwarded back and forth until a server counted too many hops and stopped it.
| Code | 5.4.6 |
| Meaning | Routing loop detected |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | With 554 |
| What the sender does | Returns the message to the sender |
| Defined in | RFC 3463 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- Two mailboxes forwarding to each other, or a forwarding rule that points back.
- Routing that sends the domain’s mail back where it came from — after a migration, or with a misconfigured connector.
What to do
- Check forwarding rules at both ends.
- For administrators: check connectors and accepted domains.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | 554 5.4.6 Message exceeded 50 hops, this may indicate an email loop. |
| Exchange | 554 5.4.6 Hop count exceeded – possible mail loop — Exchange stops a loop after 20 rounds. Exchange Online reports its own loops as 5.4.14. |
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- Fix NDR error 5.4.6 or 5.4.14 in Exchange Online — learn.microsoft.com
- DSNs and NDRs in Exchange Server — learn.microsoft.com