Blazalek.com

5.7.13User account disabled

Authentication succeeded, but the account is disabled, so the server permanently refused the attempt. 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

What this code means

Authentication succeeded, but the account is disabled, so the server permanently refused the attempt. Do not retry the same unchanged attempt.

Technical meaning

The standard X.7.13 pattern means that the client authenticated successfully, but the authenticated user account was disabled by an administrator. Code 5.7.13 applies this detail in class 5 and indicates that the failure remains permanent until the user contacts the system administrator to have the account re-enabled.

Delivery status

The leading digit 5 denotes a permanent failure of the current attempt. This is not a generic authentication failure: the credentials were accepted, but the account state blocks further operation, so entering the same passphrase again does not remove the cause.

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. Make a new, controlled attempt only after confirming that the correct account has been re-enabled or that another verified correction to its state was made; check suppression again first.

Suppression decision

Operational guidance: do not automatically add the recipient address or domain to a suppression list based on code 5.7.13 alone. Inspect the complete response, the account used for authentication, the system that returned the code, event history, and applicable policy, then make the suppression decision in that context.

Common causes

  • An administrator disabled the account for an administrative or security reason, such as nonpayment, abuse, or evidence of an attempted break-in.

Diagnostic steps

  1. Inspect the raw SMTP response or attempt report and confirm that the enhanced code is exactly 5.7.13 and that the basic reply is in the 5xx class; retain the complete response text.
  2. Correlate the response with the attempt time, client, authenticated account, and system that returned the code; use safe logs to confirm that authentication succeeded and the account was disabled instead of treating the event as a passphrase error.
  3. Stop unchanged retries; before one controlled attempt, confirm that the correct account has been re-enabled or that another material correction to its state was made, and check suppression again.

Actions by owner

Sender

  • Do not repeat the same attempt or re-enter the same credentials; contact the system administrator and provide the complete response and event time without disclosing secrets.

Sender administrator

  • Identify the account and endpoint used in the attempt, then confirm successful authentication and the account's disabled state in safe logs.
  • Resolve the verified administrative or security cause and re-enable the account only under the applicable policy; then check suppression and permit one controlled attempt.

Recipient administrator

  • If you manage the system that returned the code, inspect authentication logs and the specified account's status for the attempt time.
  • Re-enable the account only after confirming that administrative and security conditions have been met, or give the sender administrator safe context needed to resolve the matter.

Provider

  • If you operate a service involved in authentication, confirm the account state and give the appropriate administrator safe context and a re-enablement path; do not trigger automatic suppression from the code alone.

Sources and verification

The standard Tier-0 meaning of X.7.13 and the class-5 application of code 5.7.13 were verified against the IANA registry and RFC 2034 and RFC 5248 as of July 17, 2026. Diagnostic, remediation, retry, and suppression recommendations are separate operational guidance; this record contains no provider-specific practice.

  • Enumerated Status Codes / X.7.13

  • 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

Last verified:

Wojtek Blazalek

Email deliverability expert

Stuck on this error code? I help teams clear the root cause of rejections and fix authentication and reputation — so email lands in the inbox.

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