SMTP Error 553 - Mailbox name not allowed / invalid address. | Warmup Inbox

The short answer

SMTP 553 is a permanent 5xx reply defined in RFC 5321 as "requested action not taken: mailbox name not allowed", returned when the server rejects the address in MAIL FROM or RCPT TO. In practice it means either the address is syntactically invalid, or the server will not let you send from or relay through it. Fix it by correcting the address syntax and authenticating with a sender address you are allowed to use.

Quick fix

Check the address for typos and formatting errors.

5 - Permanent. The server will not try again. Fix the cause before you resend.

What it means

553 is a permanent negative completion reply. RFC 5321 section 4.2.3 defines it as "553 Requested action not taken: mailbox name not allowed (e.g., mailbox syntax incorrect)". It is returned in response to MAIL FROM or RCPT TO. The receiving or outbound server is telling you it will not accept the address you supplied, and because it is a 5xx code it is a hard failure, so retrying the same message unchanged will not help. The wording after 553 tells you which of two root causes you hit.

Common causes

How to fix it

  1. If the address is malformed, fix the syntax

    Validate the exact RCPT TO and MAIL FROM value, not the display name: one @, a real TLD, and no leading or trailing whitespace. Strip hidden characters by re-typing the address by hand rather than pasting, since addresses copied from spreadsheets or rich-text fields often carry zero-width or non-breaking spaces. Pass only the bare address into the envelope and keep any "John Doe" <...> formatting in the To header, never in the SMTP command.

  2. If the sender or relay is rejected, authenticate

    Configure SMTP AUTH with valid credentials. For Gmail or Google Workspace, use an App Password with 2-Step Verification or OAuth2, since password-only Less Secure Apps access is gone (personal accounts since May 2022, Workspace fully by May 2025). Use port 587 with STARTTLS or 465 with implicit TLS, both valid per RFC 8314.

  3. Match the From to an address you own

    Set MAIL FROM and the visible From to an address the authenticated account is authorized to send as. With Postfix smtpd_sender_login_maps, the login must be permitted for that sender.

  4. Verify envelope-from DNS for a 5.1.8

    Ensure the MAIL-FROM domain resolves with an A, AAAA, or MX record.

  5. Authenticate your domain

    Publish SPF, DKIM, and DMARC so downstream servers accept the sender.

Paired code

A real bounce often shows both a 3-digit code and an enhanced code together. This one commonly pairs with:

X.1.3 Bad destination mailbox address syntax

Common questions