Blazalek.com

5.1.2SMTP 5.1.2: The destination address was rejected

5.1.2 rejects this destination permanently. Stop unchanged retries, retain the reply, and correct the exact recipient address only when a trusted source supplies a replacement.

Category
Addressing
Class
Permanent failure
Retry
Do not retry unchanged
Suppression
Check the full context

TL;DR

Permanent destination rejection: fix the exact address; do not infer a domain-wide failure.

What this code means

RFC 3463 describes X.1.2 as a bad destination system address and permanent-only detail, but this catalog has no IANA class confirmation for the pattern. Exact Gmail 553 evidence instead rejects recipient-address syntax, a narrower provider-specific reading.

Provider examples

Gmail example
smtp;553 5.1.2 The recipient address <example@example.com> is not a valid RFC-5321 address. - gsmtp
Gmail example
553 5.1.2 The recipient address <example@example.com> is not a valid RFC-5321 address. - gsmtp

Technical meaning

The evidence supports a malformed destination address at Gmail, not a general proof that every 5.1.2 means a nonexistent domain. Read the full response.

Delivery status

Class 5 is permanent for the unchanged attempt. It does not make unrelated addresses at the domain invalid.

Class
Permanent failure
Retry
Do not retry unchanged
Suppression
Check the full context

Retry decision

Do not retry the same address. Retry only after a verified correction or a confirmed change at the identified destination system.

Suppression decision

Apply any hygiene decision to the confirmed address only. Do not automatically suppress the whole domain from a single 5.1.2 response.

Common causes

  • The provider rejects the supplied recipient address as invalid under its syntax check.

Diagnostic steps

  1. Confirm the complete reply and recipient address, then distinguish provider-specific format text from a destination-system condition.

Actions by owner

Sender

  • Stop sends to the unchanged address and obtain a correction through a trusted channel.

Sender administrator

  • Inspect source-data validation and retain the response before applying address-specific hygiene.

Sources

These sources define what this enhanced status code means, mainly through the IANA registry and related RFCs. When provider examples appear on the page, they come from that provider's published documentation. Follow the links to read the original wording in context.

Last verified:

Found an error or inaccuracy? Report a correction.

Point out the part of this page that should be checked. Every report is reviewed manually.

Type of problem

Describe the issue and, if useful, suggest corrected wording.

For a factual report, include a public source when possible.

You can submit anonymously. A reply is not guaranteed.

Do not paste full bounce messages, headers, email addresses, Message-IDs, tokens, or other personal data. Redact evidence before sending.

Sending a correction shares the information you enter with Formspree so I can review and improve this page. Read the privacy notice.

Guide

Incidents

Wojtek Blazalek

Email deliverability expert

Stuck on this error code? I help teams identify rejection causes and fix authentication and reputation, so email reaches the inbox.

Hands-on deliverability work for teams that send at scale.