534 5.7.9 Application-specific password required Email / SMTP Origin: Network OSI layer 7 · Application Last updated 4 Nov 2026

SMTP: 534-5.7.9 Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833

The Google account has 2-Step Verification on, so SMTP clients cannot use the normal password; they need an app password (or OAuth).

Exact message you may see 534-5.7.9 Application-specific password requiredApplication-specific password required534 5.7.9 Application-specific password requiredapp password required Gmail SMTPLearn more at https://support.google.com/accounts/answer/185833
Explore the map of this error Full error map →
Seen on: SMTP

Meaning

Gmail no longer accepts the account password for SMTP, IMAP and POP in most cases ("less secure apps" is gone). Create a 16-character app password for that app at myaccount.google.com/apppasswords (requires 2-Step Verification), or use OAuth 2.0. Workspace admins may block app passwords entirely.

Common causes

  • 2-Step Verification enabled and normal password used
  • App password not created or revoked
  • Workspace policy blocks app passwords
  • Typo/spaces in the app password
  • Password changed so old app passwords were removed

⚡ Quick fix

  1. Create an app password and use it as the SMTP password (no spaces)
  2. Or switch to OAuth 2.0 / an ESP
  3. Workspace admins: allow app passwords or use SMTP relay by IP

Detailed fix by platform

Linux

  1. Test a login: curl -v --url 'smtps://smtp.gmail.com:465' --user 'you@gmail.com:APP_PASSWORD' --mail-from you@gmail.com --mail-rcpt you@gmail.com -T message.txt

How to diagnose

  1. 2SV — 2-Step Verification on?
  2. Password — App password used?
  3. Admin — Workspace blocks it?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

450 4.7.1 Greylisted, please try again later — SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html (Email / SMTP)450 4.7.1 Greylisted,…451 4.3.0 Local error in processing — SMTP: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing (Email / SMTP)451 4.3.0 Local error…530 5.7.0 Authentication Required — SMTP: 530 5.7.0 Must issue a STARTTLS command first / 530 5.7.1 Authentication required (Email / SMTP)530 5.7.0 Authenticat…535 5.7.8 Username and Password not accepted — SMTP: 535-5.7.8 Username and Password not accepted. Learn more at https://support.google.com/mail/?p=BadCredentials (Email / SMTP)535 5.7.8 Username an…550 5.4.5 Daily user sending quota exceeded — SMTP: 550 5.4.5 Daily user sending quota exceeded (Gmail) (Email / SMTP)550 5.4.5 Daily user …Authentication token manipulation error — passwd: Authentication token manipulation error (Linux)Authentication token …DKIM: body hash did not verify — DKIM: dkim=fail (body hash did not verify) / signature verification failed (Email / SMTP)DKIM: body hash did n…DMARC fail: SPF and DKIM not aligned — DMARC: dmarc=fail (p=REJECT) — SPF and DKIM pass but domains are not aligned with the From header (Email / SMTP)DMARC fail: SPF and D…534 5.7.9…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.