SMTP error 449
Exchange routing error — non-standard, legacy Exchange only.
Updated Jul 1, 2026
SMTP 449 is not a standard reply code. It is a Microsoft Exchange routing error in NDRs, mapping to the RFC 3463 4.4.x (network and routing) class. It means Exchange could not route the message, usually a deleted routing group or an SMTP connector using DNS without a smart host. Fix the connector and routing-group configuration.
Correct the connector and routing-group configuration.
What it means
RFC 5321 defines no 449 reply code. "449 4.4.x" is a routing error generated internally by Microsoft Exchange and surfaced in a non-delivery report. The 4.4.x part is an enhanced status code in the network and routing class, and the leading 4 marks it transient. You see it on legacy on-premises Exchange (2000/2003), which used routing groups and link-state routing. Exchange 2007 replaced that with Active Directory site-topology routing, so a literal 449 is a legacy artifact. On modern Exchange or Exchange Online a routing failure shows up instead as codes like 451 4.4.0 (DNS query failed).
Common causes
Exchange still tries to route to a group that no longer exists, so routing fails.
Combined with a non-SMTP address space, the connector cannot resolve a next hop for the address it was given.
The address space cannot be resolved to a next hop, or a transport policy blocks or misdirects the mail.
How to fix it
- Inspect the routing table
On legacy Exchange 2000/2003, the WinRoute utility reads the link-state routing table and shows routing groups and connectors. Use it to find the dangling group or broken connector. WinRoute does not apply to Exchange 2007 or later.
- Re-home or remove orphaned recipients
If a recipient pointed at a deleted routing group, move the mailbox to a valid group or remove the stale object.
- Fix the SMTP connector
If a connector uses DNS without a smart host on a non-SMTP address space, point it at a valid smart host or correct the address space so it only handles traffic it can route.
- Validate DNS and next-hop resolution
Confirm the Exchange server's DNS resolves the relevant MX and A records. On modern Exchange, a routing stall shows as 451 4.4.0 DNS query failed; fix the DNS settings on the Send connector or server.
nslookup -q=mx domain.com - Review transport rules
Check for rules or policies rerouting or blocking the affected address space.
Common questions
Is 449 a real SMTP error code?
Not as a standard reply code. RFC 5321 does not define it. It is a Microsoft Exchange routing error in NDRs, in the RFC 3463 4.4.x network and routing class.
Why do I only see 449 on older Exchange servers?
It comes from the routing-group and link-state routing that Exchange 2000/2003 used. Exchange 2007 replaced that model, so newer versions report routing failures as codes like 451 4.4.0.
Should I still use WinRoute to fix 449?
Only on legacy Exchange 2000/2003. WinRoute does not apply to Exchange 2007 or later, or to Exchange Online.