454 is a temporary failure of either STARTTLS or AUTH, caused by the server rather than by the client’s settings. A client should not ask for the password again — it should try later.
| Code | 454 |
| Meaning | TLS not available due to temporary reason — or temporary authentication failure |
| Kind | Temporary failure — the sender tries again |
| Sent in reply to | STARTTLS or AUTH |
| What the sender does | Tries again later — or, for STARTTLS, may continue unencrypted where its policy allows |
| Defined in | RFC 3207; RFC 4954 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What to do
- Wait and try again.
- If the sender requires TLS (MTA-STS, DANE), the message waits rather than going unencrypted.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | 454 4.7.0 “Too many login attempts, please try again later” and “Cannot authenticate due to a temporary system problem”. |
| Exim | Rejects STARTTLS with 454 when its own TLS configuration has a problem. |
Sources
Checked on 27 September 2026 against these official sources:
- RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security — rfc-editor.org
- RFC 4954: SMTP Service Extension for Authentication — rfc-editor.org
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- 43. Encrypted SMTP connections using TLS/SSL — exim.org