What this code means
The receiving SMTP server permanently refused the attempt because the message's specified priority was below the lowest level the server accepts. Do not retry the same unchanged attempt.
Technical meaning
The X.7.15 pattern means that the specified priority level is below the lowest priority acceptable to the receiving SMTP server. The standard allows that the cause may be a temporary server mode in which only higher-priority messages are accepted for transfer and delivery while lower-priority messages are rejected, but code 5.7.15 reports the result in the permanent class.
Delivery status
The leading digit 5 denotes a permanent failure of the current attempt. The code does not state the accepted threshold, why it applies, or how long the server mode will last, so those details must not be inferred from the code alone.
- 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, controlled attempt only after a confirmed correction to the intended priority or after the recipient or provider confirms that acceptance conditions changed; check suppression again first.
Suppression decision
Operational guidance: do not automatically suppress the recipient address based on 5.7.15 alone. Inspect the complete response, priority used, configuration, and event history, then make the suppression decision only from the confirmed cause and applicable policy.
Common causes
- The priority level specified for the message was below the lowest level accepted by the receiving SMTP server.
- The receiving server was operating in a mode that accepts only higher-priority messages while rejecting lower-priority messages.
Diagnostic steps
- Inspect the raw SMTP response or delivery report and confirm the exact 5.7.15 code and a basic reply in the 5xx class; retain the complete response text.
- Correlate the response with the intended message, attempt time and stage, receiving endpoint, and priority level specified for that message.
- Use available configuration and logs to check the intended priority, accepted threshold, and server operating mode; do not assume those values from the code alone.
- Stop unchanged retries; after a confirmed correction or change in conditions, check suppression again and compare the outcome of one controlled attempt.
Actions by owner
Sender
- Confirm the message's intended priority and give the administrator the attempt time and complete response without repeatedly retrying it manually.
Sender administrator
- Check the priority set by the sending system, retain the attempt context, and coordinate confirmation of the accepted threshold; make a new attempt only after a confirmed correction or change in conditions.
Recipient administrator
- If you manage the server that returned the code, inspect its priority threshold, operating mode, and logs for the attempt, then correct a confirmed problem or safely state the applicable requirement.
Provider
- If you operate a service involved in the attempt, inspect managed logs and configuration for that attempt, confirm the threshold and server mode, and correct only a problem in the managed layer.
Sources and verification
The canonical Tier-0 meaning of X.7.15 and its class-5 application were verified against the IANA registry, RFC 2034, RFC 5248, and RFC 6710 as of July 17, 2026. Diagnostic, remediation, retry, and suppression recommendations are separate operational guidance; this record contains no provider-specific practice.
- iana-smtp-enhanced-status-codesT0 source
Enumerated Status Codes / X.7.15
- rfc5248T0 source
Section 2.1: registry fields and non-exclusive Associated Basic Status Code
- rfc2034T0 source
Section 4: enhanced status class agrees with SMTP reply class
- rfc6710T0 source
IANA registry reference for X.7.15
Last verified:
