Skip to content
Standard SMTP codes · permanent error

5.7.13: user account disabled

The login itself worked, but the account has been disabled by its administrator, so the server will not accept mail from it until it is re-enabled.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.7.13
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
5.7.13 User Account Disabled

What it means

RFC 5248 registered X.7.13 for an account that authenticated correctly but has been disabled, for example for non-payment, abuse or a suspected break-in, and associates it with reply code 525. It tells the client that the failure is permanent until the user contacts the administrator. Typing the password again will not help, which is what separates it from 5.7.8. The code concerns the sender's own account on its submission server, so the people to contact are the provider or the IT team that runs it.

Common causes

  • The provider suspended the account for non-payment or a terms violation.
  • The account was locked after signs of compromise, such as a burst of spam.
  • An administrator disabled the account, for example when an employee left.

How to fix it

  1. 01Contact your email provider or IT team to find out why the account was disabled.
  2. 02If it was compromised, change the password and review sign-ins and forwarding rules once it is restored.
  3. 03Use another account to send in the meantime.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 535 5.7.8Login failed: invalid credentials.The SMTP server rejected the login because the username, password or token was wrong or not sufficient, so it will not accept mail from this session.StandardPermanent
  2. 5.2.1Mailbox disabled.The recipient's mailbox exists but has been switched off and is refusing messages, for a while or for good depending on the class of the code.StandardPermanent
  3. 535Authentication credentials invalid.The server rejected the login because the username, password or token is wrong or not sufficient for this account, so no mail is sent.StandardPermanent

5.7.13 at other providers

  1. 550 5.7.13No permission to post to the public folder.Delivery to a mail-enabled public folder failed because the permission the sender falls under does not allow creating items in it.MicrosoftPermanent

All 105 standard codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer