Skip to content
Gmail and Google Workspace · permanent error

535 5.7.8: username and password not accepted

Google rejected the user name and password your client used to sign in to its SMTP server, so it will not send mail for it.

Gmail
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
535 5.7.8
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
535 5.7.8 Username and Password not accepted.

What it means

This is Gmail's answer to failed SMTP authentication. Either the credentials are wrong, or they are the account's normal password in an app where Google requires something else: Google no longer accepts plain passwords from most third-party apps, which need an app password (available with 2-Step Verification) or OAuth sign-in. Google's current table prints this code as 5.7.80; the June 2025 version read 5.7.8, the code this entry uses and the one IANA registers for invalid authentication credentials.

Common causes

  • A wrong user name or password, or an outdated one.
  • The account's normal password used in an app, where Google requires an app password or OAuth.
  • An app password that was revoked, or created for another account.

How to fix it

  1. 01Check that the user name is the full email address, and enter the password again.
  2. 02Turn on 2-Step Verification and create an app password for the client, or switch it to OAuth sign-in.
  3. 03Sign in to the account in a browser to clear any security block.
  4. 04For devices that can do neither, use the Workspace SMTP relay with IP-based authentication.

Sources

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

  1. 534 5.7.9App password required.The account uses 2-Step Verification, so Google will not accept its normal password from your mail client and asks for an app password instead.GmailPermanent
  2. 534 5.7.14Sign in through a web browser first.Google refused your client's SMTP sign-in and wants the account owner to sign in through a web browser before the client tries again.GmailPermanent
  3. 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
  4. 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

5.7.8 at other providers

  1. 535 5.7.8Authentication failed for an external address.Fastmail could not sign in to the outgoing server of an external address you send from, most often because its stored password has changed.FastmailPermanent

All 108 Gmail 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