Blazalek.com

5.7.2SMTP 5.7.2: Mailing list expansion prohibited

The system permanently refused the message because the sender was not authorized to send to the intended mailing list. Do not retry the same unchanged attempt.

Category
Security, authentication and policy
Class
Permanent failure
Retry
Do not retry unchanged
Suppression
Check the full context

TL;DR

Permanent rejection: the sender cannot post to the intended mailing list. Coordinate list permissions with the list administrator before resending. Usually an authorization issue, not list hygiene, but repeated blocks warrant a policy review. Do not retry unchanged.

What this code means

Posting to the intended mailing list is unauthorized for this sender, so list expansion for that submission is prohibited; registry pattern X.7.2 appears as code 5.7.2 for that refusal. In the enhanced status register this list-authorization detail is permanent, and the standard assigns X.7.2 exclusively to that permanent form. The numeric reply describes a mailing-list posting refusal, not a broader mailbox or routing fault, and by itself it neither names the posting rule nor proves the list address is invalid.

Technical meaning

Unauthorized sending of a message to the intended mailing list is what X.7.2 covers. The standard says this detail is useful only as a permanent error, and code 5.7.2 applies it in class 5.

Delivery status

The leading digit 5 denotes a permanent failure of the current attempt. The code describes an authorization refusal for a list, but by itself it does not identify the specific rule or establish that the list address is invalid.

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

Retry decision

Operational guidance: stop automatic and manual retries of the same unchanged attempt. Consider a new send only after a verified change to the sender identity, its authorization, or the applicable list rule; check suppression again before the attempt.

Suppression decision

Operational guidance: do not automatically add the list address or domain to a suppression list based on 5.7.2 alone. Inspect the complete response, list-authorization context, event history, and applicable policy, then make the suppression decision in that context.

Common causes

  • The system serving the intended mailing list determined that the sender was not authorized to send a message to it.

Diagnostic steps

  1. Inspect the raw SMTP response or nondelivery report and confirm that the enhanced code is exactly 5.7.2 and that the basic reply is in the 5xx class; retain the complete response text.
  2. Correlate the event with the intended message, attempt time, sender identity used, intended list, transaction stage, and system that returned the code; identify the applied rule from available logs instead of inferring it from the code alone.
  3. Stop unchanged retries; before a controlled new send, verify a material change to authorization, identity, or the list rule and check suppression again.

Actions by owner

Sender

  • Do not resend the same unchanged message; confirm the intended sender identity and list, then give the administrator the complete response.

Sender administrator

  • Retain the complete response and attempt context, inspect the sender identity and sending-path configuration used, and coordinate with the list administrator to identify the authorization that requires correction.

Recipient administrator

  • If you manage the list, inspect the posting rules and sender authorization applied to the specified attempt; correct them only if they do not match the intended policy.

Provider

  • If you operate a system involved in the attempt, inspect managed-service logs and the applied rule, then give the administrators safe context needed to verify the appropriate correction.

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

  • Deliverability

    SPF/DKIM/DMARC and related auth policy are required for inbox delivery.

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.