SMTP error 543
Not a real code — a mislabel of enhanced status 5.4.4 "unable to route".
Updated Jul 1, 2026
SMTP 543 is not a real SMTP reply code. RFC 5321 section 4.2.3 defines a fixed set of three-digit replies and 543 is not among them. The label conflates a routing failure with enhanced status X.4.4 "unable to route" (RFC 3463), usually a DNS or MX problem. Fix it by reading the server actual reply text and verifying the recipient domain MX records resolve.
Verify the recipient domain MX / DNS records resolve.
What it means
There is no 543 reply code. RFC 5321 section 4.2.3 ("reply codes in numeric order") lists the 5xx permanent-failure replies as 500, 501, 502, 503, 504, and 550 through 555, with 521 and 556 added later by RFC 7504. None of them is 543. The number comes from the enhanced status system in RFC 3463, where codes look like X.4.4 ("unable to route") and are written with dots, not as a bare three-digit number. A real routing bounce reads like "550 5.4.4 Unable to route: no MX record found", where 550 is the RFC 5321 reply code and 5.4.4 is the enhanced code. Tools and SEO pages collapsed "5.4.x routing" into a fictional "543", so treat it as a mislabel and read the actual reply line.
Common causes
Per RFC 3463 section 3.5, class X.4.x is network and routing status, and X.4.4 means the system could not determine the next hop because routing information was unavailable, in practice a DNS or MX lookup that returned nothing usable (for example only an SOA record).
The leading digit signals severity: 4.4.4 is a temporary routing failure worth retrying, and 5.4.4 is permanent.
DNS can resolve on your laptop but fail on the mail server, from split-horizon DNS, a broken resolver, or an outbound firewall blocking port 53.
A misconfigured Postfix transport_maps, Exim router, or smart host produces a local "unable to route" rather than a remote bounce.
How to fix it
- Capture the full reply
Get the exact line from your MTA or provider logs: the real reply code (421, 450, 550, and so on) plus the enhanced code (4.4.4 or 5.4.4) and the text. That text is the ground truth, not "543".
- Check the recipient domain MX records
Run "dig MX recipient-domain.com +short" or "nslookup -type=MX recipient-domain.com". If nothing returns, the domain has no mail route, so confirm the address and domain are spelled correctly and the domain still exists.
- Account for the A or AAAA fallback
Per RFC 5321 section 5.1, a domain with no MX records is treated as having an implicit MX at its own host, so senders use its A or AAAA record. If neither MX nor address records resolve, delivery cannot be routed, the classic X.4.4 condition.
- Test resolution from the sending host
Verify DNS from the host that actually sends, not just your workstation, since split-horizon DNS, a broken resolver, or a blocked port 53 can differ between them.
- If you operate the routing, check the transport
For an on-prem MTA, confirm the route or relay host for the destination is defined and reachable. Note that some sources call "543" an invalid or blocked recipient, which overlaps with 550 5.1.1 and is a different diagnosis, so let the enhanced code decide whether it is routing (5.4.x) or a bad address (5.1.x).
Paired code
A real bounce often shows both a 3-digit code and an enhanced code together. This one commonly pairs with:
Common questions
Is 543 a valid SMTP reply code?
No. RFC 5321 section 4.2.3 defines the valid three-digit codes and 543 is not one of them. The valid 5xx codes there are 500, 501, 502, 503, 504, and 550 through 555, with 521 and 556 added by RFC 7504. "543" is a mislabel, usually for enhanced status X.4.4 ("unable to route").
What does the routing failure that 543 refers to actually mean?
X.4.4 "unable to route" means the mail system could not determine the next hop because DNS or MX information was unavailable. 4.4.4 is transient and worth retrying; 5.4.4 is permanent.
How do I check if a domain has a mail route?
Run "dig MX recipient-domain.com +short". If it returns nothing, check for an A or AAAA record too, since a domain with no MX falls back to its own address record. If neither resolves, the domain has no deliverable mail route.