Gmail IMAP Not Working in 2026? Fix Your Email App

It is a familiar jolt: you open Thunderbird, Apple Mail, or whatever desktop client runs your day, expecting your inbox, and instead a red banner stares back — "Authentication failed." Your password is typed correctly. Nothing on the machine has changed. Yet the mail will not budge. If that describes your morning, welcome to the single most common Gmail headache going around right now. Gmail IMAP not working in a third-party program has turned into a routine complaint across r/Gmail and the Google Workspace forums, and almost none of those threads end with "oh, I mistyped my password."

The real culprit is a gradual, multi-year tightening of the rules that govern how outside software is allowed to reach Gmail. The old habit of typing a password into any app has been retired; Google now demands modern, token-based sign-in. Below, you will find exactly why the Gmail IMAP not working warning keeps popping up in 2026, the server addresses and ports you ought to be typing, and the two repairs — OAuth 2.0 sign-in and 16-character app passwords — that get your mail flowing again in a matter of minutes. Running one personal mailbox or a whole stable of aged Gmail accounts for outreach, this is the connectivity cheat sheet worth bookmarking.

What "Gmail IMAP Not Working" Really Means in 2026

IMAP — the Internet Message Access Protocol — is the standard that lets an outside email program read and manage the messages that live on Gmail's servers. SMTP, or Simple Mail Transfer Protocol, is its sending-side sibling. When somebody says their Gmail IMAP not working, they are almost certainly describing one of three things: the client refuses to log in at all, it logs in but never fetches new mail, or it downloads fine but won't send.

Here is the crucial twist for 2026: in the vast majority of cases, the protocol itself is in perfect working order. Gmail's IMAP and SMTP servers are online and doing their job. What has changed is authentication — the way your app proves it is entitled to open the mailbox. For most applications, Google simply will not accept a plain username and password anymore. When your client stubbornly keeps trying that legacy handshake, Gmail turns it away, and the app hands you a woolly sync error. That single mismatch is, by a wide margin, the number-one reason a Gmail IMAP not working message shows up nowadays.

Once this clicks, you save yourself hours of pointless troubleshooting. You do not need to reinstall your OS, buy a new mail client, or abandon Gmail. The only thing that has to change is how the connection proves itself. Fix that, and the identical app that was throwing errors a minute ago starts syncing immediately.

Why Google Locked Out Your Third-Party App

For years, any program could log into Gmail with nothing more than your email address and password. Google called this "less secure app" access, and it was a phisher's dream — one stolen password unlocked your entire inbox. Starting in late 2024 for personal accounts, and fully enforced across Google Workspace by May 2025, Google switched that door off permanently.

What replaced it is OAuth 2.0, a token-based approach: you sign in once through Google's own secure prompt, and the app receives a revocable token in place of your actual password. That token can be tightly scoped and cancelled at any moment, and your password never leaves your hands. It is a real security upgrade — but it also means any older app configured for "regular password" sign-in stops dead. That is precisely how a client you have happily used for a decade can suddenly throw a Gmail IMAP not working error overnight, with nothing changed on your end.

This is part of a wider 2026 shift. Across the board, providers are locking down free, password-based IMAP access to slow automated abuse and credential-stuffing runs. Google's move gets the loudest reaction only because Gmail is the largest mailbox on Earth, but the direction of travel is identical industry-wide. That same authentication crackdown is exactly why senders now have to be more meticulous than ever about correct configuration — something we dug into in our guide to the Gmail 550-5.7.26 unauthenticated-sender error.

The Exact Error Messages You'll Run Into

Neither Gmail nor your client tends to spell out "switch to OAuth." Instead you get vaguer alarms. Once you can recognize them, you know instantly that authentication — not your network — is what's broken:

• "Authentication failed" when connecting to imap.gmail.com — the classic Thunderbird line.
• "Username or password is incorrect" when it clearly isn't — Gmail rejecting a legacy password login.
• "[AUTHENTICATIONFAILED] Invalid credentials" — the raw reply direct from the IMAP server.
• "Cannot get mail — the connection to the server failed" on an iPhone or Mac.
• "Web login required" or a prompt that never finishes — Gmail asking you to complete a browser sign-in.

Seeing any of these is a strong sign you have hit the OAuth 2.0 wall. A true network outage looks different: timeouts, "server not found," or the same failure striking every account and app at once. If Gmail alone is affected and you're confident the password is correct, you are looking at the modern Gmail IMAP not working pattern, and the fixes ahead will sort it out.

Step 1: Confirm IMAP Is Turned On in Gmail

Before you touch your client, make sure Gmail is actually offering IMAP in the first place. On most accounts it's on by default, but the switch can end up flipped off — especially on Workspace accounts an administrator manages.

1. Open Gmail in a browser and click the gear icon → See all settings.
2. Go to the Forwarding and POP/IMAP tab.
3. Under "IMAP access," select Enable IMAP.
4. Click Save Changes at the bottom.

On a Google Workspace domain, IMAP and POP can also be controlled centrally from the Admin console under Apps → Google Workspace → Gmail → End User Access. If IMAP is disabled there, nothing you change inside your client will help until an admin re-enables it. Checking this first rules out the most trivial cause of a Gmail IMAP not working complaint before you pour time into authentication.

Step 2: Punch In the Correct IMAP & SMTP Settings

A surprising share of sync failures come down to a mistyped port or the wrong encryption setting. Gmail's official server details have not changed, so copy these exactly:

Two things trip people up. First, the username must be your whole email address, not just the part before the @. Second, encryption has to be SSL/TLS — never "none." If your client shows "Normal password" as the authentication method and you aren't feeding it an app password, that is very likely the source of your Gmail IMAP not working error. Right ports with the wrong auth type still fails, so treat settings and authentication as two separate boxes to tick.

Fix A: Switch Your Client to OAuth 2.0 Sign-In

This is the cleanest, most durable fix, and it is exactly the route Google wants you on. Every current client — recent Thunderbird, Apple Mail, the new Outlook, Samsung Mail — supports it. The wrinkle is that you often have to re-add the account, because an old profile built around password login will keep reaching for the dead method.

1. Remove the Gmail account from your client entirely (don't just edit it).
2. Add it back as a fresh account, typing only your Gmail address.
3. When Google's own sign-in window pops up, log in there and grant access.
4. The client stores a revocable OAuth token and connects normally.

As you re-add, set the authentication type to OAuth2 (Thunderbird labels it exactly that) instead of "Normal password." If your client offers a "Sign in with Google" button, click it — that button is OAuth 2.0. This single change clears the great majority of Gmail IMAP not working reports, because it swaps the rejected legacy login for the method Gmail now insists on. Even with two-step verification and passkeys enabled, OAuth still works without a hitch; our Gmail passkeys guide walks through how those pieces fit together.

Fix B: Create a 16-Character App Password

A few clients — older Outlook desktop builds, some scanners, printers, CRMs, and scripts — cannot do OAuth 2.0 at all. For those, Google offers app passwords: a single 16-character code that stands in for your real password for one specific app. It is the officially blessed workaround whenever a Gmail IMAP not working error comes from a client that will never support modern sign-in.

The catch: app passwords require 2-Step Verification to be switched on for the account first. If you can't see the option anywhere, that's why. Here's how to do it:

1. Head to myaccount.google.com → Security and turn on 2-Step Verification if it's off.
2. Return to Security and open App passwords (type it into the account search bar if it's tucked away).
3. Name it something like "Outlook Desktop" and click Create.
4. Copy the 16-character code Google shows you (the spaces don't matter).
5. In your email client, paste that code into the password field in place of your usual password.

Treat the app password like any genuine credential — whoever holds it can read your mail. Make one per device, so that revoking a single lost laptop doesn't knock everything else offline. For anyone pushing SMTP at volume, app passwords are the foundation of the whole setup; we cover that end to end in our guide to Gmail SMTP accounts for bulk sending.

Client by Client: Thunderbird, Outlook, Apple Mail

The precise steps differ a little between apps. Here are the specifics for the three that generate the most Gmail IMAP not working questions.

Mozilla Thunderbird. Thunderbird's OAuth handling is first-rate. Right-click the account → Settings → Server Settings, and change "Authentication method" to OAuth2. If it still balks, remove the account and re-add it so Thunderbird launches a fresh Google sign-in window. When Thunderbird worked yesterday and not today, a revoked or expired OAuth token is the usual reason — re-authenticating fixes it.

Microsoft Outlook. This is the sorest spot of all. Classic Outlook desktop does not support OAuth 2.0 for IMAP or POP connections, and Microsoft has said it has no plans to add it. That leaves you two options: (1) move the account into the new Outlook or Outlook on the web, both of which handle Google OAuth properly, or (2) stay on classic Outlook and sign in with a 16-character app password. There is no third path — a classic-Outlook Gmail IMAP not working error won't clear with password tinkering alone.

Apple Mail (Mac & iPhone). Apple Mail supports OAuth, so the cure is almost always to remove and re-add the account. Open Settings → Mail → Accounts (or System Settings → Internet Accounts on a Mac), delete the Google account, then add it back through "Add Account → Google," which triggers the correct sign-in. That resolves the overwhelming majority of "Cannot get mail" errors on iOS and macOS.

Still Broken? The Less Obvious Causes

If your settings are right and you're on modern authentication yet the problem hangs around, run through these subtler suspects:

• IMAP connection limit. Gmail allows a maximum of 15 simultaneous IMAP connections per account. When several devices and apps all hammer the same mailbox, fresh connections get refused. Close duplicate clients or trim how many folders each device syncs.
• Revoked or expired token. A password change, a security event, or a long spell of inactivity can invalidate an OAuth token. Signing in again mints a new one.
• Blocked sign-in attempt. Check myaccount.google.com → Security → Recent security activity. If Google flagged your client as suspicious, approve it there and try again.
• Too many messages in one folder. A label or folder stuffed with tens of thousands of messages can choke the initial sync. Let it run its course, or narrow which folders sync.
• Antivirus or firewall interference. Some security suites proxy email traffic and break SSL on ports 993/465. Temporarily disable email scanning to test.
• Workspace policy. On business domains, an admin might restrict IMAP or require specific apps. Confirm with your administrator.

Working through these methodically clears the stubborn cases where the standard OAuth and app-password fixes didn't quite finish the job on their own.

Keeping Bulk and Business Accounts Connected

If you operate a lot of mailboxes — for outreach, support queues, or marketing — the authentication changes hit harder, because every single account has to be reconnected the modern way. A handful of habits keep a large pool steady and stop a wave of Gmail IMAP not working failures from sweeping your whole fleet:

• Standardize on OAuth 2.0 clients. Choose apps and tools that support Google sign-in natively, so you aren't wrangling dozens of app passwords by hand.
• One app password per device wherever OAuth is off the table, stored in a secure vault, so a lone revocation never cascades.
• Turn on 2-Step Verification everywhere — it's a prerequisite for app passwords and a sound baseline security measure anyway.
• Respect the 15-connection limit by not pointing too many tools at a single mailbox.
• Warm and age accounts properly so they trip the security flags that block sign-ins far less often.

Account age and reputation matter here too: established, well-warmed mailboxes attract fewer suspicious-activity blocks than brand-new ones. That reliability is a big part of why marketers lean on aged Gmail accounts, and it pairs naturally with the connection discipline above. For the security side of running many inboxes, our Gmail account security tips cover the routines that keep large pools healthy. And if you rely on pulling mail in from other providers, keep an eye on the separate 2026 change we documented in Gmail ending Gmailify and POP, which affects fetching in a different way.

Frequently Asked Questions

Why is my Gmail IMAP not working when I'm sure the password is right?

Because Gmail no longer accepts a bare password from most apps. Since 2024–2025, Google has required OAuth 2.0 token sign-in and has shut down legacy "less secure app" access. Your password can be flawless and the login can still fail. The fix is to re-add the account with "Sign in with Google" (OAuth 2.0), or, for clients that can't manage that, to use a 16-character app password with 2-Step Verification enabled.

What are the correct Gmail IMAP and SMTP server settings?

For incoming mail, use imap.gmail.com on port 993 with SSL/TLS. For outgoing mail, use smtp.gmail.com on port 465 (SSL) or 587 (TLS/STARTTLS). Your username is your full email address, and authentication should be OAuth 2.0 or an app password — never "normal password" without one. Correct ports paired with the wrong authentication type is a common reason Gmail IMAP is not working.

Do I still need an app password if I'm already using OAuth 2.0?

No. OAuth 2.0 and app passwords are two separate roads to the same place, and you only need one. If your client supports "Sign in with Google," use OAuth — it's more secure and renews itself. App passwords exist solely for older clients like legacy Outlook desktop, printers, or scripts that can't perform modern sign-in. Never configure both on the same account.

Why does Outlook keep failing with Gmail when other apps are fine?

Classic Outlook desktop doesn't support OAuth 2.0 for IMAP and POP, and Microsoft has said it won't add it. That's why a Gmail IMAP not working error can turn up in Outlook alone while Apple Mail and Thunderbird work perfectly. Either move the account to the new Outlook or Outlook on the web, which support Google sign-in, or authenticate classic Outlook with a 16-character app password.

Is Gmail IMAP being discontinued in 2026?

No. IMAP itself isn't going away. What ended is password-based ("less secure app") login. IMAP and SMTP remain fully supported as long as your app authenticates with OAuth 2.0 or an app password. The 2026 story is about how you connect, not whether you can. Move to modern authentication and IMAP works exactly as it always has.

Gmail IMAP not working is, almost every time, an authentication problem in disguise — and it's fixable in minutes once you spot it. Enable IMAP, enter the right ports, and move your client to OAuth 2.0 sign-in — or an app password for the stubborn legacy apps. Do that and your inbox syncs the way it used to. Want a hand getting your clients connected, or looking for reliable, well-aged Gmail accounts that stay stable across email apps? Message us on Telegram at @oldgmb and our team will point you toward the right setup for your workflow.