334 is the server’s next question in a login: a Base64-encoded challenge — often just “Username:” or “Password:” encoded — that the client answers with one Base64 line. The exchange ends with 235 (success) or an error.
| Code | 334 |
| Meaning | Server challenge (authentication continues) |
| Kind | Waiting for more |
| Sent in reply to | AUTH |
| What the sender does | Sends the Base64 answer, or “*” to cancel |
| Defined in | RFC 4954, section 4 |
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.
Worth knowing
The exchange ends with 235, 535 (wrong credentials), 534 (method too weak), 538 (encryption required), 454 (temporary failure) or 501 (cancelled or garbled).
Sources
Checked on 27 September 2026 against these official sources:
- RFC 4954: SMTP Service Extension for Authentication — rfc-editor.org
- RFC 2034: SMTP Service Extension for Returning Enhanced Error Codes — rfc-editor.org