On this page
Short answer
534 5.7.9 is Gmail's reply when an app logs in to SMTP with the regular Google password on an account that has 2-Step Verification. The text reads Application-specific password required. Connect the app with Sign in with Google if it offers that; otherwise create an app password and enter it in place of the account password. Nothing is sent until the login works.
What the error says
Google's Gmail SMTP errors and codes lists three 534 replies for sign-in:
Code | Text in the reply | Google's help link |
|---|---|---|
534 5.7.9 | "Application-specific password required." | Sign in with app passwords |
534 5.7.9 | "Please log in with your web browser and then try again." | Can't sign in to your Google Account |
534 5.7.14 | "Please log in through your web browser and then try again." | Can't sign in to your Google Account |
Google's table prints the first two codes as 5.7.90. RFC 4954 defines the status as 5.7.9, and sending tools show it that way: Smartlead's help article quotes it as "Invalid login: 534-5.7.9 Application-specific password required." In the reply, the link with ?p=InvalidSecondFactor opens Google's app passwords page.
The two browser texts ask for a browser sign-in to that account before the app tries again. This page covers the first text.
What 5.7.9 means
RFC 4954 calls 534 5.7.9 "Authentication mechanism is too weak": the selected mechanism "is weaker than server policy permits for that user," and the client "SHOULD retry with a new authentication mechanism." The policy is per account, so 534 5.7.9 Application-specific password required means this account won't take a plain password.
For an account with 2-Step Verification, Gmail offers two ways in over SMTP. One is OAuth 2.0: per Google for Developers, "The SASL XOAUTH2 format enables clients to provide OAuth 2.0 credentials for authentication." The other is an app password, "a 16-digit passcode that gives a less secure app or device permission to access your Google Account" (Google Account Help).
Why Gmail asks for it
Google's app passwords page explains: "When you use 2-Step Verification, some less secure apps or devices may be blocked from accessing your Google Account. App passwords are a way to let the blocked app or device access your Google Account."
Smartlead's article describes the same case: the error appears when a Gmail account is connected "via SMTP/IMAP and your Google account has 2-Step Verification (2FA) enabled." The trigger is 2-Step Verification on the account plus its regular password in the tool's password field.
When the app password option is missing
Google lists three reasons the option can be absent:
"Your Google Account has 2-Step Verification set up only for security keys."
"You're logged into a work, school, or another organization account."
"Your Google Account has Advanced Protection."
In those cases, connect the tool with Sign in with Google. Google recommends it in any case: app passwords "aren't recommended and are unnecessary in most cases."
How to fix it
Check whether the tool offers Sign in with Google. In Instantly it is Option 1: oAuth under Email Accounts > Add or Buy Accounts > Connect existing accounts (Instantly help). Smartlead's Gmail guide recommends Google OAuth over an app password.
If it doesn't, create an app password. Open myaccount.google.com/apppasswords, name it after the tool and copy the passcode. You can generate a new one any time.
Enter it in place of the account password. Smartlead's steps for this error: Email Accounts, select the account with the error, paste the app password into the password field, save and reconnect. In Instantly the flow is Option 2: App Password (Instantly help).
Give each tool its own app password. When you drop a tool, remove its entry on the same Google page: after that, "the app can't access your Google Account again."
Expect to repeat this after a password change. Google revokes app passwords when the account password changes. If the reconnect then fails with "Username and Password not accepted", see 535 5.7.8.
Server addresses and ports are in Gmail SMTP server address.
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
Fifty Google mailboxes on app passwords means fifty passcodes, and each one is revoked by a password change on its account. Instantly's OAuth guide says that once a Workspace admin marks the app as Trusted, you can connect all Google accounts from the same Workspace. For a set of Workspace mailboxes, that is one admin step and then a Google sign-in per mailbox. A password change still signs these out: Google revokes OAuth tokens with mail access when the user's password changes (Google), so any reset means signing in again.
The list and the copy can stay as they are, because the error is about the login. Once the mailbox sends again, Gmail sending limits apply.
Questions
Is 534 5.7.9 the same as 535 5.7.8?
No. 534 5.7.9 says the account needs another way to sign in. 535 5.7.8 says the credentials themselves were rejected: a mistyped or revoked app password, or a regular password Google no longer accepts.
Should I turn off 2-Step Verification instead?
That won't bring password logins back. Google's transition guide says SMTP on Workspace "will no longer work with legacy passwords (basic authentication)", and Gmail Help says Gmail "no longer supports third-party apps or devices which require you to share your Google username and password." Use Sign in with Google or an app password.
What we recommend at Outreach2day
We don't sell Gmail or Google Workspace mailboxes, so this fix applies to Google accounts you run yourself. Outreach2day mailboxes are standard SMTP/IMAP on our own infrastructure, with their own SMTP/IMAP logins that work in any sending tool.
Sources
- Google Workspace Admin Help: Gmail SMTP errors and codes: knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- Google Account Help: Sign in with app passwords: support.google.com/accounts/answer/185833
- RFC 4954: SMTP Service Extension for Authentication: rfc-editor.org/rfc/rfc4954
- Google for Developers: IMAP, POP and SMTP: developers.google.com/workspace/gmail/imap/imap-smtp
- 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: Automatic OAuth 2.0 token revocation upon password change: knowledge.workspace.google.com/admin/apps/automatic-oauth-20-token-revocation-upon-password-change
- Smartlead Help: Google Error 534-5.7.9 Application-specific password required: helpcenter.smartlead.ai/en/articles/42-google-error-invalid-login-534-579-application-specific-password-required
Related answers
- What Does 535 5.7.8 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
- Why Are My Cold Emails Going to Spam in Gmail in 2026?Gmail and Google
- What Does a 550 5.7.1 Bounce Mean, and How Do I Fix It?Bounces and errors
In depth on the blog
- Gmail SMTP Server Address, Ports and Settings6 min read
- Gmail Sending Limits: Free Gmail, Workspace, Relay and API14 min read

