Clear explanations, real-world troubleshooting steps, and the checks that matter before you change your sending configuration.
535 generally means authentication was rejected. 530 often means authentication or a secure session is required before continuing. 454 often indicates a temporary authentication or TLS-related failure. The text after the code and any enhanced status code matter: providers can use the same three-digit code for different conditions.
What each SMTP code means
| Code | Typical interpretation | First investigation |
|---|---|---|
| 535 | Authentication credentials or method rejected | Username format, password/app password, account restrictions, supported AUTH method |
| 530 | Authentication required, or STARTTLS required before AUTH | Command order, encryption mode and whether the client authenticated |
| 454 | Temporary authentication failure or temporary TLS problem | Provider outage, rate limiting, TLS negotiation and retry guidance |
SMTP uses reply classes: 5xx usually signals a permanent failure for the current attempt, while 4xx generally signals a temporary failure. That distinction should change your retry behavior. A 535 caused by an invalid app password is unlikely to be fixed by immediate repeated retries; a 454 may resolve after a provider-side issue clears.
Identify the exact failing step
Before changing settings, capture a sanitized SMTP transcript or your mail client's debug log. Record the hostname, port, TLS mode, UTC timestamp, SMTP command that preceded the error, full reply text and enhanced code (such as 5.7.8) if present. Never paste credentials, AUTH payloads or session tokens into a support ticket.
220 mail.example.net ESMTP ready EHLO client.example.com 250-mail.example.net 250-STARTTLS 250 AUTH PLAIN LOGIN STARTTLS 220 Ready to start TLS [encrypted TLS session begins] EHLO client.example.com 250 AUTH PLAIN LOGIN AUTH [redacted] 535 5.7.8 Authentication credentials invalid
This sample shows that the connection and TLS negotiation succeeded. The failure is at authentication, so firewall and DNS troubleshooting are lower-priority than checking credentials and account policy. Actual server capabilities and wording vary.
Fixing 535: authentication rejected
- Check the username format. Some providers require the complete email address; others require an account ID or a dedicated SMTP username. An alias may not be a valid login even if it can receive mail.
- Verify the credential type. An SMTP/API credential is not always the same as the web-login password. Some providers require an app password or SMTP-specific token.
- Check account permissions. SMTP submission may be disabled by plan, security policy, administrator setting or suspicious-login controls.
- Confirm the authentication mechanism. Inspect the server's post-TLS EHLO capabilities and use a method the provider supports. Do not assume LOGIN is available everywhere.
- Stop repeated blind retries. Multiple failed logins can trigger temporary lockouts or security alerts. Test once after each verified configuration change.
If the same credentials work in a provider's own test client but not in your application, compare the exact host, port, TLS mode and username. The difference may be configuration rather than password validity.
Fixing 530: authenticate or encrypt first
A common sequence error is attempting MAIL FROM before successful authentication on a submission server. Another is attempting AUTH before the provider's required STARTTLS upgrade. Review the full response text: 530 Authentication required and 530 Must issue STARTTLS first point to different fixes.
For submission on port 587, a common configuration is an initial plaintext SMTP connection followed by STARTTLS before authentication. On port 465, TLS usually begins immediately on connection. These are common conventions, not universal provider guarantees. Match the provider's documented settings and verify the negotiated TLS session; do not disable certificate verification as a workaround.
Fixing 454: temporary failure
First inspect whether the response refers to temporary authentication unavailability, a rate limit, or a TLS problem. Confirm whether the same error occurs from another authorized client and whether the provider reports an incident. If the service is temporarily unavailable, use bounded exponential backoff rather than a rapid retry loop.
If the message specifically mentions TLS, check the client library's supported TLS versions, certificate trust and the provider's current encryption requirements. A TLS handshake failure is not the same as a wrong SMTP password.
A safe five-minute diagnostic checklist
- Confirm the SMTP submission host is correct, not the IMAP host or a marketing landing-page domain.
- Match port 587/STARTTLS or 465/implicit TLS to the provider's published configuration.
- Record the complete error message and which command triggered it.
- Check the SMTP username and whether the account needs a separate app password or SMTP credential.
- Verify account access and provider security settings, then perform one controlled test.
- If the error persists, send sanitized logs and a UTC timestamp to the provider.
Authentication works, but messages still fail?
A successful AUTH reply only proves the server accepted your login. It does not prove the sender address is authorized, the recipient was accepted, or the message reached the inbox. If submission succeeds but placement is poor, investigate SPF, DKIM and DMARC alignment and the difference between SMTP acceptance and inbox placement. For connection-level issues, use the SMTP connection testing guide and port 465 versus 587 guide.
Frequently asked questions
Does SMTP error 535 always mean the password is wrong?
No. It can also indicate the wrong username format, unsupported authentication mechanism, disabled SMTP access or an account security restriction. The provider's detailed response is more useful than the three-digit code alone.
Should I change from port 587 to 465 to fix 535?
Not automatically. If the session already reached AUTH and received 535, verify credentials and account policy first. Change ports only when your provider's documented settings require it.
Can I retry a 454 error?
Often yes, after a delay, because 4xx replies are generally temporary. Use a capped retry policy and investigate persistent failures instead of retrying indefinitely.
Build a healthier sending foundation
InboxWarmup helps teams plan and manage manual email warmup while monitoring the factors that influence sender trust. Warmup cannot guarantee inbox placement, and authentication errors must be resolved at the provider or configuration level.
Explore InboxWarmup plans