X.7.13 · Security or policy
SMTP enhanced status code 5.7.13
User Account Disabled
X.7.13 means the account you authenticated with has been disabled, for reasons such as non-payment or abuse. It is permanent until an administrator re-enables it.
| Registry code | X.7.13 |
|---|---|
| Forms in use | 5.7.13 |
| Registry name | User Account Disabled |
| Subject | 7: Security or policy |
| Permanent or temporary | 5.x.x permanent failure: resending unchanged will not succeed |
| Associated basic codes | 525 |
| Defined in | [RFC 5248] |
What the registry says
Sometimes a system administrator will have to disable a user's account (e.g., due to lack of payment, abuse, evidence of a break-in attempt, etc). This error code occurs after a successful authentication to a disabled account. This informs the client that the failure is permanent until the user contacts their system administrator to get the account re-enabled. It differs from a generic authentication failure where the client's best option is to present the passphrase entry dialog in case the user simply mistyped their passphrase.
IANA SMTP Enhanced Status Codes registry, X.7.13
In practice
X.7.13 comes after a successful login to an account that has been disabled, for example for non-payment, a compromise or abuse. Re-entering the password will not help. Microsoft uses 5.7.13 and 5.7.135 for a public folder that rejects outside senders, a different meaning.
What the sender should do
Contact the provider or administrator of the sending account. Changing the password will not help.
Would verifying the list have prevented 5.7.13?
No
This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Common questions
- What does 5.7.13 mean?
- X.7.13 means the account you authenticated with has been disabled, for reasons such as non-payment or abuse. It is permanent until an administrator re-enables it.
- What should I do about 5.7.13?
- Contact the provider or administrator of the sending account. Changing the password will not help.
- Would an email verifier have caught 5.7.13?
- No. This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Sources
- IANA: SMTP Enhanced Status Codes registry (checked 2026-11-05)
- RFC 3463: Enhanced Mail System Status Codes (checked 2026-11-05)
Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.
SimpleVerifier Team · Last checked against the sources 2026-11-05