🎉 Limited Time Offer: 70% OFF
on all Monthly Plans for First Month.

5.x.x permanent failure

SMTP Error Code 553: Meaning, Causes and How to Fix It

SMTP 553 is a permanent failure.

The mailbox name is not allowed, usually because the address is malformed, the domain is wrong, or the receiver will not accept mail addressed that way.

Class
5xx permanent
Bounce type
Hard bounce
Highest severity
Medium
Responses on record
6

SMTP 553 responses from email providers

How mailbox providers phrase a 553. Open a provider for the full text, severity and fix for every variation.

SMTP 553 responses from spam filters

How spam-filtering gateways phrase a 553 rejection.

SMTP 553 questions

›Is SMTP 553 a hard bounce or a soft bounce?

It is a permanent failure, so a hard bounce. The receiving server will not accept the same message on a retry, and the address or the sending problem has to be fixed before you resend.

›What causes an SMTP 553 error?

The mailbox name is not allowed, usually because the address is malformed, the domain is wrong, or the receiver will not accept mail addressed that way. The exact reason varies by receiver, which is why this page lists the specific 553 responses recorded for Email Security.cloud, Google, Yahoo Inc, Zoho.

›How do I fix an SMTP 553 bounce?

Read the enhanced status code and the message text, not just the number. Wording that names the recipient (user unknown, mailbox unavailable) means correct or remove the address. Wording that names authentication or reputation (SPF, DKIM, DMARC, blocklist) means fix that on the sending side, or clear the listing. Every response on this page has its own guidance.

Other SMTP error codes