554 5.4.6 Routing loop detected (too many hops)
Quick answer
The message bounced between mail servers too many times, usually because of conflicting forwarding rules, and was rejected to prevent an endless loop.
Recommended action: Suppress the address
Common causes
- Two mail servers each forwarding to the other for the same address.
- Misconfigured auto-forwarding rule creating a cycle.
What to do
This is a mail routing problem, usually on the recipient domain's side, that the sender cannot fix. Suppress the address if it persists, and let the recipient's IT team know if you have a direct relationship.
How to read 554 5.4.6
554 is the basic SMTP reply defined in RFC 5321. 5.4.6 is the enhanced status code from RFC 3463, which reads as class, subject and detail:
- Class
- 5Permanent failure
- Subject
- .4Network and routing
- Detail
- .6Routing loop detected (too many hops)
Further reading
FAQ
Frequently asked questions
Is this a common bounce type?
No. It is one of the rarer bounce codes and usually appears only when a domain's own forwarding setup is broken, not because of how the message was sent.
Stop hard bounces before they start
Upload a list or call the API, and send only to addresses that can receive mail. Unknown results are always free.
100 free credits · No card required · Credits never expire