Skip to content
Standard SMTP codes · permanent error

500 5.5.6: authentication data too long

During login, the client sent an authentication response longer than the server can accept for the chosen method, so the AUTH command failed.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
500 5.5.6
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
500 5.5.6 Authentication Exchange line is too long

What it means

RFC 4954, which defines SMTP authentication, added X.5.6 for one case: the client's base64 response in the AUTH exchange is longer than the server's buffer for the selected mechanism. The RFC pairs it with reply code 500 and notes it can be permanent or temporary; in practice it reads 500 5.5.6. It happens at login, before any message is sent, so it affects every message from that client until it is fixed. Long credentials, such as OAuth access tokens, are one way to reach the limit.

Common causes

  • A very long credential or token sent in one AUTH response.
  • A server with a small buffer for the selected mechanism.

How to fix it

  1. 01Try another authentication mechanism the server offers.
  2. 02Update the mail client or library, which may handle long tokens differently.
  3. 03Check that the token or password is the one you expect; a corrupted value can be much longer than normal.
  4. 04Ask the server's administrator whether the limit can be raised.

Sources

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

  1. 500Command not recognised.The server did not recognise the command it received, or the command line was too long. This is a permanent error in the SMTP conversation.StandardPermanent
  2. 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
  3. 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
  4. 5.5.2SMTP syntax error.A command from the sending software could not be understood, because its syntax was wrong or the command was not recognised at all.StandardPermanent

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