Configure Outlook for Gmail Using POP3

Configuring Outlook to connect to Gmail via POP3 has more steps than it used to because Google removed the simple username/password authentication option. You now need to enable POP3 in Gmail, then either use OAuth (Outlook's auto-discovery handles this for IMAP/Exchange but not always for POP3) or generate an app password. This guide covers the full procedure.

A note up front: IMAP is the better choice for almost all Gmail-in-Outlook setups. POP3 makes sense only if you specifically want a local-only archive and won't access Gmail from any other device.

Step 1: Enable POP3 in Gmail

By default, Gmail does not enable POP3. Turn it on first:

1. Open Gmail in a web browser
2. Click the gear icon → See all settings
3. Click the Forwarding and POP/IMAP tab
4. Under POP Download, select Enable POP for all mail (or "for mail that arrives from now on")
5. Under "When messages are accessed with POP," choose what Gmail does with downloaded messages — keep them in inbox, archive, mark as read, or delete (recommend: keep in inbox)
6. Click Save Changes

POP3 is now enabled for the account. The same steps work for Google Workspace accounts unless the admin has disabled POP/IMAP at the tenant level.

Step 2: Generate an app password (if 2FA is enabled)

If you have 2-Step Verification enabled on your Google account (you should), regular passwords don't work for POP3. Generate an app password:

1. Go to myaccount.google.com/security
2. Confirm 2-Step Verification is On (required to use app passwords)
3. Scroll to or search for App passwords (or visit myaccount.google.com/apppasswords)
4. Sign in again if prompted
5. Enter a name for the app password (e.g., "Outlook Desktop")
6. Click Generate
7. Copy the 16-character password shown — you'll need it for Outlook

App passwords bypass 2FA for specific applications. Generate a new one if you ever need to rotate or revoke access.

If you don't have 2FA enabled, Google has likely disabled basic password authentication entirely for your account. The fix is to enable 2FA and use app passwords. There is no path to "less secure apps" anymore.

Step 3: Configure Outlook

In Outlook for Windows:

1. File → Account Settings → Account Settings
2. Click New under the Email tab
3. Enter your Gmail address, click Advanced options → check "Let me set up my account manually," then Connect
4. Select POP
5. Configure:

Field	Value
Incoming mail server	pop.gmail.com
Incoming Port	995
Incoming encryption	SSL/TLS
Outgoing mail server	smtp.gmail.com
Outgoing Port	465 (or 587)
Outgoing encryption	SSL/TLS (or STARTTLS for 587)

6. Enter username (full Gmail address) and the app password
7. Make sure "Outgoing server requires authentication" is checked, using the same credentials
8. Click Connect, complete test

After the account is added, configure the leave-on-server setting:

1. File → Account Settings → Account Settings
2. Select the Gmail POP3 account → Change → More Settings
3. Advanced tab
4. Check "Leave a copy of messages on the server"
5. Optional: check "Remove from server after X days" — set 30+ days for headroom
6. Click OK

Without this setting, Outlook will delete messages from Gmail after downloading them. They'll vanish from Gmail web, mobile, and any other client.

Step 4: Test

Send a test message to and from the account:

• Send to: verify it arrives in Outlook
• Send from: verify it appears in your Sent folder and the recipient gets it
• Check Gmail web after Outlook downloads: messages should still be present (proves leave-on-server is working)

If sending fails with "authentication failed," the SMTP password isn't right. Double-check the app password.

Alternative ports

If port 465 doesn't work (corporate firewall, etc.):

• SMTP port 587 with STARTTLS
• POP3 port 110 with STARTTLS (NOT recommended — weaker security than 995)

For POP3, always prefer 995 with SSL. For SMTP, 465 and 587 are equivalent in practice.

Daily sending limits

Gmail enforces send limits even via SMTP:

Account type	Daily limit	Per-message recipients
Free Gmail	500/day	500
Google Workspace	2,000/day	2,000
Google Workspace via SMTP relay	10,000/day per user	10,000

Hitting the limit triggers a 24-hour cooldown — you can't send through SMTP until it resets. If you're sending more than 100/day, you've outgrown Gmail SMTP for the use case. Use a transactional ESP like Postmark, Mailgun, or Amazon SES — see SMTP settings reference.

Practitioner note: I get clients asking how to "scale Gmail sending past 500/day" — the answer is don't. Gmail's SMTP relay isn't designed for bulk sending, and the limit is there for a reason. Use the right tool for the job: ESPs are designed for volume sending and cost a few dollars per thousand messages.

Why POP3 is rarely the right answer

For Gmail specifically, POP3 has significant downsides:

• Folder structure doesn't sync (Gmail labels are lost)
• Conversations don't group properly
• Sent mail in Outlook doesn't sync back to Gmail Sent (unless you also bcc yourself)
• Mobile Gmail app shows different state than Outlook
• Multi-device access is broken

IMAP avoids all of these. The configuration is similar:

Setting	IMAP value
Incoming	imap.gmail.com:993 SSL
Outgoing	smtp.gmail.com:465 SSL

Use the same Gmail address and app password.

For more detail on choosing between protocols, see IMAP vs SMTP.

Outlook auto-discovery for Gmail

Newer Outlook builds can sometimes auto-configure Gmail accounts using OAuth instead of manual settings. The flow:

1. File → Add Account → enter Gmail address → Connect
2. Outlook redirects to Google's sign-in page (browser opens)
3. Sign in to Google, grant permission to Outlook
4. Outlook completes setup automatically

This uses OAuth (modern authentication) instead of password — no app password needed. It defaults to IMAP, not POP3. If you specifically want POP3, you have to use the manual setup above.

Common errors and fixes

"Outlook cannot connect to your incoming POP3 mail server." Check that POP3 is enabled in Gmail Settings and that port 995 with SSL is configured.

"Authentication failed" with POP3. App password missing, expired, or wrong. Regenerate at myaccount.google.com/apppasswords.

"The connection to the server is interrupted." Check that 2FA is enabled and an app password is in use. Without 2FA, Google's "less secure apps" is no longer an option for most accounts.

Sending fails but receiving works. SMTP authentication not enabled or different credentials. In Outlook → Account Settings → More Settings → Outgoing Server tab, "My outgoing server requires authentication" must be checked, and the credentials should match the incoming account.

Messages disappearing from Gmail. Leave-on-server not enabled. POP3 default is to delete after download. Fix in More Settings → Advanced.

Same message downloaded multiple times. Outlook's "Use Cached Exchange Mode" doesn't apply to POP3. The "downloaded ID" cache may be corrupted — easiest fix is to remove and re-add the account.

If you're configuring Outlook with Gmail at scale (multiple users, different requirements) or migrating from POP3 to IMAP, book a consultation. Mailbox configuration is a frequent piece of audit work.

Sources

• Google — Read Gmail Messages on Other Email Clients Using POP
• Google — Sign in With App Passwords
• Microsoft — Add a Gmail Account to Outlook
• Google Developers — Use IMAP and SMTP to Read and Send Gmail
• RFC 1939: POP3
• RFC 8314: TLS for Email Submission and Access

---

v1.0 · May 2026