On this page
Short answer
535 5.7.8 means the SMTP server refused your login: RFC 4954 defines 5.7.8 as invalid authentication credentials. At Gmail it reads 535 5.7.8 Username and Password not accepted. Usually the tool sends the regular Google password where Google expects Sign in with Google or an app password, or a password change revoked the app password. No email went out, so fix the login and resend.
What the error says
535 5.7.8 is the server's answer to the login, before any message is handed over. RFC 4954 names it "Authentication credentials invalid": the server refused the AUTH command "due to invalid or insufficient authentication credentials." The sequencer shows it as an account error, and no prospect received anything.
The words after the code depend on the server:
Server | Text after 535 5.7.8 | Documented in |
|---|---|---|
Gmail and Google Workspace | "Username and Password not accepted." | |
Postfix servers | "Error: authentication failed:" plus a reason |
Gmail's reply ends with a help link containing ?p=BadCredentials and the tag gsmtp, which Google adds to all its SMTP errors. Google's reference table prints the status as 5.7.80; RFC 4954, and the bounces people paste into forums, have 5.7.8. The email bounce decoder reads both.
What it means on any SMTP server
RFC 4954 tells the client to "ask the user to supply new credentials", so retrying the same password won't help. Outside Google, check the username format your provider asks for, the password, and the port and encryption from its setup page. On Microsoft 365 the refused login reads 535 5.7.3 instead. If you run the server, the log has the reason: Postfix logs "SASL ... authentication failed" with the username it tried before it sends the 535.
Two codes look similar and mean something else. 454 4.7.0 is a temporary failure, and the RFC says the client "SHOULD NOT prompt the user for another password" for it. 530 5.7.0 "Authentication required" means the tool tried to send without logging in.
Why Gmail refuses the login
The tool sends your regular Google password. Gmail Help says Gmail "no longer supports third-party apps or devices which require you to share your Google username and password." On Google Workspace, SMTP "will no longer work with legacy passwords (basic authentication)", per Google's transition guide.
The app password was revoked. "We revoke your app passwords when you change your Google Account password" (Google Account Help). A reset by you or by a Workspace admin ends every app password on that account.
The username is incomplete. Google's device and app setup page asks for "your complete Google Workspace email address" and an app password.
2-Step Verification is on. Gmail has a separate code for this case, 534 5.7.9 "Application-specific password required"; see 534 5.7.9.
How to fix it
Copy the full error from the sequencer. Confirm the code and that the server is smtp.gmail.com. Ports and settings are in Gmail SMTP server address.
Use Sign in with Google if the tool offers it. Google recommends it over app passwords. In Instantly: Email Accounts > Add or Buy Accounts > Connect existing accounts > Google > Option 1: oAuth (Instantly help). On Workspace, the guide has the admin trust the app first: Security > Access and data control > API Controls > Manage app access > Configure new app, search by Instantly's client ID, then Trusted. Smartlead's Gmail guide also recommends Google OAuth.
If the tool only takes a password, create a new app password. With 2-Step Verification on, open myaccount.google.com/apppasswords, name the app and copy the passcode. Use it with the full address for SMTP and IMAP.
Reconnect the account. In Smartlead: Email Accounts, tick the accounts, the settings icon at the top right of the table, then (Re)connect Emails (Smartlead help). In Instantly, connect it with one of the two methods above.
If IMAP fails too on Workspace, ask the admin to check Apps > Google Workspace > Gmail > End User Access. With IMAP off, users "can't get their email with POP or IMAP email clients" (Google).
Resend once the login works. Per Smartlead, emails "won't be sent from the particular email accounts until you reconnect".
Free guide19 min read
Send 100,000 cold emails a month
Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.
What it means for cold email
A 535 is about the sending account. The server stopped at the login, so your list, copy and domain reputation played no part, and the prospects can stay in the campaign.
With dozens of Google mailboxes in one sequencer, watch for 535s arriving in a batch. Google revokes an account's app passwords whenever its password changes, so a password reset across a Workspace organization breaks every affected mailbox at once. One failing mailbox points to that account alone.
Don't let the tool retry in a loop: Google's table also lists 454 4.7.0 "Too many sign-in attempts, try again later." Pause the account, fix the login, reconnect once. Rate limits and spam filtering have their own codes, such as 421 4.7.28; volume caps are in Gmail sending limits.
Questions
Is 535 5.7.8 a block on my domain?
No. It answers the AUTH command, which RFC 4954 does not permit during a mail transaction, so Gmail rejected the login before any message was offered. Reputation problems come back as other codes, such as 550 5.7.1.
Can I turn "less secure app access" back on?
No. Google's admin help says "The less secure apps enforcement setting is no longer available in the Google Admin console" (Google). Connect with Sign in with Google, or with an app password if the tool has no Google sign-in.
What we recommend at Outreach2day
Outreach2day mailboxes are standard SMTP/IMAP on our own infrastructure, and their logins work in any sending tool. Google's app password and OAuth rules cover Gmail and Google Workspace accounts, which we don't sell; for those accounts, the steps above are the fix.
Sources
- Google Workspace Admin Help: Gmail SMTP errors and codes: knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- RFC 4954: SMTP Service Extension for Authentication: rfc-editor.org/rfc/rfc4954
- Gmail Help: Add Gmail to another email client: support.google.com/mail/answer/7126229
- Google Account Help: Sign in with app passwords: support.google.com/accounts/answer/185833
- Google Workspace Admin Help: Transition from less secure apps to OAuth: knowledge.workspace.google.com/admin/sync/transition-from-less-secure-apps-to-oauth
- Google Workspace Admin Help: Control access to less secure apps: knowledge.workspace.google.com/admin/apps/control-access-to-less-secure-apps
- Postfix source: smtpd_sasl_glue.c: github.com/vdukhovni/postfix/blob/master/postfix/src/smtpd/smtpd_sasl_glue.c
Related answers
- What Does 534 5.7.9 Mean, and How Do I Fix It?Gmail and Google
- What Does Gmail's 421 4.7.28 Error Mean, and How Do I Fix It?Gmail and Google
- What Does a 550 5.7.1 Bounce Mean, and How Do I Fix It?Bounces and errors
- Why Are My Cold Emails Going to Spam in Gmail in 2026?Gmail and Google
In depth on the blog
- Gmail SMTP Server Address, Ports and Settings6 min read
- SMTP for Cold Email: Mailbox, Relay or Self-Hosted7 min read

