553 5.1.3 Invalid mailbox name syntax
Quick answer
The receiving server rejected the address because its local part (before the @) does not follow that server's mailbox naming rules.
Recommended action: Suppress the address
Common causes
- Typo introducing an invalid character.
- Address copied with extra whitespace or formatting artifacts.
- A domain-specific restriction on characters in local parts.
What to do
Remove or correct the address. Syntax checks before sending should catch most of these, so if they are reaching this stage, add verification to your signup or import flow.
How to read 553 5.1.3
553 is the basic SMTP reply defined in RFC 5321. 5.1.3 is the enhanced status code from RFC 3463, which reads as class, subject and detail:
- Class
- 5Permanent failure
- Subject
- .1Addressing
- Detail
- .3Invalid mailbox name syntax
Further reading
FAQ
Frequently asked questions
Why does this happen after a valid-looking syntax check?
The general syntax rules (RFC 5321 and 5322) are permissive and allow characters many mail servers do not support. An address that is valid under the spec can still be rejected by a stricter server.
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