How to Use Gmail With a Third-Party Email Client

If you have ever tried to read Gmail in a client other than Google's own web interface or mobile app, you have probably hit at least one of three surprises: a password that the client rejects even though you typed it correctly, the same email appearing four or five times across different folders, or a delete key that archives instead of removes. None of those are bugs in your client. They are the result of Gmail implementing IMAP differently from every other mail server, and the fixes are straightforward once you know what is happening.

This guide covers three things: how to authorize the connection in the first place, what Gmail's IMAP behavior actually is and why it differs from what a standard client expects, and what to fix when something breaks. Google Workspace users should note one additional prerequisite: your administrator must enable IMAP for the organization in the Admin console before any of these steps will work for you.

The short answer#

Connecting Gmail to a third-party email client takes two setup steps and one credential choice. First, enable IMAP inside Gmail settings — it is off by default on new accounts. Second, authorize the client to access your account, either through Google's OAuth sign-in or through an app password if the client uses legacy credentials.

OAuth is Google's preferred method and what every modern client supports. You click Sign in with Google inside the client, a browser window opens to Google's own sign-in page, you approve the requested access, and the client receives a secure token. Your Gmail password is never exposed to the client. App passwords serve legacy clients that cannot handle OAuth: generate a 16-character code at myaccount.google.com/apppasswords, enter it as the password field, and use your full Gmail address as the username. App passwords require two-step verification to be active on the account first.

Either way, the server settings are: incoming server imap.gmail.com, port 993, SSL/TLS required; outgoing SMTP server smtp.gmail.com, port 465 with SSL or port 587 with STARTTLS. Once the connection is established, Gmail's label-based architecture introduces folder behaviors that differ from what a standard IMAP client expects — those are covered after the step-by-step instructions.

What you need before you start#

Three conditions must be in place before the connection attempt will succeed. Checking them now saves a round-trip through a credential error.

• IMAP must be enabled in Gmail. Go to Settings (the gear icon, top right) > See all settings > Forwarding and POP/IMAP > IMAP access > Enable IMAP > Save Changes. It is disabled by default.
• Google Workspace accounts: your administrator must enable IMAP access for the organization in the Google Admin console. If the IMAP toggle is missing from your Gmail settings, that is the reason.
• App password users: two-step verification must be active on your Google Account before the app password option appears at myaccount.google.com/apppasswords.
• Confirm the client supports IMAP, not POP only. IMAP syncs and leaves mail on the server; POP downloads and can remove it. This guide covers IMAP.
• OAuth users: any client built or substantially updated after 2022 supports Google sign-in. If the client presents only a server address and a plain password field with no OAuth option, it cannot connect — Google removed plain-password IMAP access in May 2022.

How to connect Gmail to a third-party email client#

1. 1

   Enable IMAP in Gmail settings

   Open gmail.com and click the gear icon in the top right, then See all settings. Go to the Forwarding and POP/IMAP tab. Under IMAP access, select Enable IMAP. Scroll down and click Save Changes. This step is required even for clients that sign in through OAuth — the IMAP connection still needs to be enabled server-side.

2. 2

   Choose and prepare your authentication method

   Modern clients: look for a Sign in with Google or Add Gmail account option and use it. Legacy clients that ask only for a server address and password: open myaccount.google.com/apppasswords, select Mail and the device type, click Generate, and copy the 16-character code immediately. You will only see it once.

3. 3

   Add the account in your email client

   For OAuth: click Add Account, choose Google or Gmail, enter your email address, and follow the browser prompt to grant access. For app passwords: click Add Account, choose IMAP or Other, enter your full Gmail address as the username, and paste the 16-character app password into the password field. Do not enter your regular Gmail password here — it will fail.

4. 4

   Enter IMAP and SMTP server details if prompted

   Incoming IMAP: imap.gmail.com, port 993, SSL/TLS. Outgoing SMTP: smtp.gmail.com, port 465 (SSL/TLS) or 587 (STARTTLS). Clients that completed OAuth authorization typically auto-populate these; skip the step if the fields are already filled.

5. 5

   Wait for the initial sync and review the folder list

   Gmail creates one IMAP folder per label, plus a set of special folders under [Gmail]: All Mail, Sent Mail, Drafts, Spam, Starred, Trash, and Important. Expect a longer folder list than you are used to on other providers. The next section explains what each folder represents and how to reduce the list.

6. 6

   Set the delete behavior you actually want

   In Gmail, go to Settings > Forwarding and POP/IMAP > IMAP settings. Under When I mark a message in IMAP as deleted and expunge the inbox, choose the behavior that matches your expectation: archive the message (Gmail default, which surprises most IMAP users), move it to Trash, or delete it immediately. Set this once before you start using the client.

How Gmail behaves differently over IMAP#

Gmail was designed around labels, not folders. IMAP was designed around folders. Gmail bridges the two by translating every label into an IMAP folder view — but the translation produces behaviors no standard IMAP client was built to handle. These six behaviors account for almost every complaint about Gmail in a third-party client.

The root cause of most Gmail-IMAP friction is one architectural fact: every message is stored once in All Mail, and labels are applied as additional folder views on top of that single store. A client that syncs every available folder downloads the same message once per label it carries. Knowing this makes every duplicate and delete problem immediately diagnosable — and the fix is always the same: tell the client which folders to sync and which to ignore.

What to do when it does not work#

Most Gmail-plus-IMAP problems fall into one of six patterns. The table below maps each symptom to its cause and the fix. If your situation is not covered, Google's Gmail Help pages on reading Gmail through other email clients are current and address Workspace admin restrictions, rate limits, and less common connection errors.

A faster way: a client built for Gmail's architecture#

The steps above establish a working IMAP connection. What they do not solve is the ongoing work that comes after the connection is set up: deciding which messages need a response, writing replies, tracking follow-ups before they go cold. A generic IMAP client reads mail and leaves the rest to you.

We build AI Emaily, an AI-native email client that connects Gmail through Google's standard OAuth sign-in and handles the IMAP quirks automatically — duplicate suppression, correct delete behavior, full label-to-folder mapping — without any manual folder configuration. Beyond the connection, AI Emaily triages incoming mail down to a short ranked list of what needs you, drafts replies in the voice you configure through your Personal Context brain and per-client profiles, and surfaces follow-ups before threads go quiet. Manual, Copilot, and Autopilot modes let you set how much the agent acts on your behalf, with undo and a full audit trail on every action. There is a 7-day free trial — see the details at aiemaily.com/pricing.