538 means the chosen login method — typically PLAIN or LOGIN — may be used only over an encrypted connection. Modern servers rarely send it: they simply do not offer those methods until TLS is up.
| Code | 538 |
| Meaning | Encryption required for requested authentication mechanism |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | AUTH |
| What the sender does | Starts TLS, then logs in again |
| Defined in | RFC 4954, section 6 |
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
- Use STARTTLS on port 587, or implicit TLS on port 465, before logging in.
What each provider means by it
| Who | What they say |
|---|---|
| Postfix | With smtpd_tls_auth_only, does not offer or accept login over an unencrypted connection at all. |
Worth knowing
RFC 4954 keeps 538 for historical purposes: servers should not advertise a method they will refuse for lack of encryption.
Sources
Checked on 27 September 2026 against these official sources:
- RFC 4954: SMTP Service Extension for Authentication — rfc-editor.org
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Postfix Configuration Parameters — postfix.org