Skip to content
Gmail and Google Workspace · permanent error

534 5.7.14: sign 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.

Gmail
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
534 5.7.14
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
534 5.7.14 Please log in through your web browser and then try again.

What it means

Google wants the account owner to sign in on the web before it lets an app sign in over SMTP. In a browser Google can show checks and prompts that an SMTP client cannot display; until the owner deals with them, SMTP sign-ins fail with this reply. Google links it to its help for people who cannot sign in to their Google Account. Signing in through a browser and clearing any prompt usually lets the app back in. If the app signs in with the account's normal password, it may also need an app password or OAuth.

Common causes

  • Google wants to verify the account owner before it allows SMTP sign-ins.
  • A security prompt or alert on the account is waiting for the owner.
  • The app signs in with a normal password that Google no longer accepts from it.

How to fix it

  1. 01Sign in to the account in a web browser and complete any checks Google shows.
  2. 02Review recent security activity on the account.
  3. 03Switch the app to an app password, or to OAuth sign-in if it supports it.
  4. 04Try the app again after signing in.

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.9Sign in with a web browser first.Google refused your client's SMTP sign-in and wants the account owner to sign in through a web browser first, where Google can run its checks.GmailPermanent
  2. 535 5.7.8Username 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.GmailPermanent

Further reading

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