Reading time: 12 min · Last verified: July 2026 · SMTPedia editorial team
To connect Gmail to Outlook, Thunderbird, Apple Mail, a mobile app, or a WordPress SMTP plugin, you need three things: the incoming server (IMAP or POP3), the outgoing server (SMTP), and the right authentication. The first two are simple. The third is where every failed setup happens.
Since May 2022, Google has disabled “Less Secure App” access entirely. Your regular Gmail password no longer works in mail clients, and it will not work again. You have two paths: turn on 2-Step Verification and generate an App Password (16 characters, one per client), or use OAuth 2.0 through a client that supports it. This guide covers both, plus the current server addresses, sending limits, and the specific error messages you will see if something is misconfigured.
Your Gmail password no longer works in mail clients. Google removed access for what it called “Less Secure Apps” and now requires either an App Password (16-character token generated after enabling 2-Step Verification), or a client that supports OAuth 2.0. If your setup fails with authentication error 535 5.7.8 Username and Password not accepted, this is the reason. See the Security Prerequisites section below for setup steps.
Quick Gmail Email Settings Summary
Gmail email settings are the IMAP, POP, and SMTP server details you need to connect your Gmail or Google Workspace account to clients like Outlook, Apple Mail, Thunderbird, WordPress, and mobile apps.
| Protocol | Server | Port | Encryption |
|---|---|---|---|
| IMAP (incoming) | imap.gmail.com | 993 | SSL/TLS |
| POP (incoming) | pop.gmail.com | 995 | SSL/TLS |
| SMTP (outgoing) | smtp.gmail.com | 465 (SSL) or 587 (TLS/STARTTLS) | SSL or STARTTLS required |
Use this guide for: Gmail email settings for Outlook, iPhone, Android, Thunderbird, WordPress SMTP plugins, and other IMAP/SMTP clients.
Quick orientation on the three protocols: IMAP and POP control how your client downloads and syncs incoming messages, while SMTP handles outgoing mail. If you use multiple devices, you want IMAP. If you use one device and want offline copies, POP still has a purpose. Either way you need SMTP to send.
Gmail Access Methods: Web, IMAP, POP, SMTP
Gmail Web vs Email Clients
Gmail’s web interface is often enough for casual users, but power users, teams, and businesses frequently need full desktop clients, automation tools, or WordPress to send and receive mail. That is where IMAP/POP/SMTP come in: they allow third‑party software to connect to Gmail securely.
Using a client can unlock offline access, advanced filtering, calendar integration, and unified inboxes. The trade‑off is that you must configure the correct Gmail email settings and keep them aligned with Google’s security policies.
IMAP vs POP for Gmail
Gmail supports both IMAP and POP, but IMAP is the recommended choice for almost all modern setups. IMAP synchronizes mail between devices by keeping the master copy on Gmail’s servers, while POP is a download‑and‑store model intended for one primary device.
| Protocol | Devices | Storage Model | Best For |
|---|---|---|---|
| IMAP | Multiple devices (desktop, mobile, web) | Messages stay on Gmail; changes sync everywhere. | Most users; Outlook, Apple Mail, Thunderbird, mobile apps. |
| POP | Primarily one device | Messages download to client; can optionally be removed from Gmail. | Offline archives, backup/exports, storage management. |
Security Prerequisites (2FA, App Passwords, OAuth)
Enabling 2‑Step Verification & App Passwords
Like Yahoo, Google strongly encourages 2‑Step Verification (2FA). When 2FA is on, many legacy IMAP/SMTP clients and WordPress plugins can’t use your main password; they require an app‑specific password instead. An app password is a 16‑character code generated in your Google account that you paste into the client instead of your usual password.
Before configuring Gmail in desktop clients or WordPress SMTP plugins, log into your Google account in a browser, turn on 2‑Step Verification, and generate an app password for “Mail” on the device/app you are configuring.
OAuth vs Password‑Based Logins
Modern clients such as recent Outlook versions, Apple Mail, Thunderbird, and WP Mail SMTP’s Gmail mailer support OAuth, where you sign in via a Google window instead of entering the server password directly. OAuth is more secure and handles token refreshes automatically.
Prefer OAuth wherever possible, and reserve app passwords for older clients, simple SMTP libraries, and WordPress plugins that cannot use OAuth yet.
Gmail IMAP Settings (Recommended Default)
Step 1: Enable IMAP in Gmail
To use IMAP, you must enable it in Gmail:
- On a computer, open Gmail in a browser and click the settings gear → See all settings.
- Go to the Forwarding and POP/IMAP tab.
- Under IMAP access, select Enable IMAP.
- Click Save Changes at the bottom of the page.
Gmail IMAP Server Settings
Once IMAP is enabled in Gmail, use these server settings in your email client:
| Field | Value |
|---|---|
| IMAP server | imap.gmail.com |
| Port | 993 |
| Encryption | SSL/TLS required |
| Authentication | Required (normal password, app password, or OAuth) |
| Username | Your full Gmail or Workspace email address |
| Password | Your account password or app password (if 2FA is enabled) |
Gmail POP Settings (For Specific Use Cases)
Step 1: Enable POP in Gmail
If you need POP access:
- In Gmail settings, open the Forwarding and POP/IMAP tab again.
- Under POP download, choose:
- Enable POP for all mail, or
- Enable POP for mail that arrives from now on.
- Decide what Gmail should do with messages after they’re accessed via POP (keep, mark read, archive, or delete).
- Click Save Changes.
Gmail POP Server Settings
Use these settings in the POP account section of your client:
| Field | Value |
|---|---|
| POP server | pop.gmail.com |
| Port | 995 |
| Encryption | SSL/TLS required |
| Authentication | Required (password or app password) |
| Username | Your full Gmail or Workspace email address |
| Password | Your account password or app password |
When POP Still Makes Sense
POP can be useful when you want a one‑time offline archive, need to export mail to another system, or intentionally keep Gmail storage minimal by deleting messages from the server after download. For multi‑device access and day‑to‑day use, IMAP remains the better choice.
Gmail SMTP Settings (Sending Mail from Clients & Apps)
Core Gmail SMTP Server Settings
Use these settings for SMTP when configuring Gmail in any client or plugin:
| Field | Value |
|---|---|
| SMTP server | smtp.gmail.com |
| Port (SSL) | 465 |
| Port (TLS/STARTTLS) | 587 |
| Encryption | SSL or STARTTLS required |
| Authentication | Required (password, app password, or OAuth) |
| Username | Your full Gmail or Workspace email address |
| Password | Your account password or app password (if 2FA is on) |
Sending as @gmail.com vs Custom Domain
For personal Gmail addresses, SMTP uses your @gmail.com identity by default. For Google Workspace, SMTP uses your custom domain address (for example, you@yourcompany.com) and can support aliases configured in the Gmail “Send mail as” settings.
For transactional and bulk sending, Gmail’s SMTP is limited. As volume and automation grow, it is safer to move newsletters and high‑volume campaigns to a dedicated SMTP relay or ESP while reserving Gmail for user mailboxes and low-volume application mail.
About Gmail
gmail.comgooglemail.comGmail is the email service of Google, launched publicly on April 1, 2004 (initially by invitation only). At launch, Gmail broke market conventions by offering 1 GB of free storage when competitors offered 2 to 25 MB, alongside a search-centric interface built on the same technology as Google Search itself. The service reached general availability in 2007.
With an estimated 1.8 billion active users worldwide, Gmail is the largest single email provider by mailbox count and represents 27 to 31 percent of global email opens tracked by client analytics. The service runs on Google's proprietary infrastructure with automatic spam filtering trained on cross-account signals. Gmail is offered as a free consumer service (15 GB shared with Google Drive and Photos) and as part of Google Workspace for businesses (starting at 30 GB and going up to 5 TB per user).
Gmail supports IMAP, POP3, and SMTP for third-party client access, plus native APIs for Google Workspace integrations. Since 2022, Google has progressively deprecated basic password authentication in favor of OAuth2 and app-specific passwords for accounts with two-factor authentication enabled.
Timeline
- 2004Launched by invitation only with 1 GB free storage
- 2007Public availability
- 2009Left beta after five years
- 2012Passed 425 million active users
- 2016Reached 1 billion monthly active users
- 2020G Suite rebranded to Google Workspace
- 2022Basic authentication deprecation begins
- 2024Enforcement of bulk sender rules (SPF/DKIM/DMARC + one-click unsubscribe)
Gmail's 1 GB launch offering was reportedly considered an April Fools' joke by many observers on April 1, 2004; it was real. The service also pioneered conversation view (threading), keyboard shortcuts, and the promotions/social tabs. Gmail Workspace domains inherit Google's deliverability reputation, which is a factor in why many businesses run their transactional email through Google infrastructure.
WordPress SMTP Plugin Configuration
Configuring Gmail SMTP in WP Mail SMTP

WordPress sites often fail to send mail when they rely on PHP’s mail() function. Using the WP Mail SMTP plugin with Gmail fixes this by routing mail through Gmail’s authenticated SMTP with OAuth or app passwords.
- Install and activate the WP Mail SMTP plugin from the WordPress repository.
- Go to WP Mail SMTP → Settings → General and set your From email and From name.
- Under Mailer, choose the Google / Gmail option.
- Option A, One‑Click Setup (Pro): follow the on‑screen authorization flow to connect to your Google account; WP Mail SMTP will handle OAuth and credentials for you.
- Option B, Manual web app setup:
- In the WP Mail SMTP settings, note the required redirect URI.
- In Google Cloud Console, create an OAuth web app, add the redirect URI, and copy the Client ID and Client Secret.
- Paste the Client ID and Client Secret into WP Mail SMTP and complete the authorization.
- Scroll down and click Save Settings, then send a test email from the plugin to confirm deliverability.
Configuring Gmail SMTP in MailPoet
If you use MailPoet for newsletters inside WordPress, you can connect it to Gmail’s SMTP for low‑volume sending. However, be mindful of Gmail’s daily sending limits and avoid large campaigns through this route.
- In your WordPress dashboard, go to MailPoet → Settings → Send With.
- Select Other or SMTP as the sending method.
- Enter:
- SMTP host:
smtp.gmail.com - Port: 587 (TLS) or 465 (SSL)
- Encryption: TLS/SSL
- Username: your Gmail/Workspace address
- Password: app password (recommended when 2FA is enabled)
- SMTP host:
- Save changes and send a MailPoet test email.
For high‑volume newsletter sending, consider moving to a dedicated SMTP or ESP and keep Gmail for transactional or low‑volume messages.
Configuring Gmail IMAP & SMTP in Email Clients
This section targets long‑tail searches like “gmail email settings for outlook / thunderbird / mailbird / em client / mailspring / postbox”. Every client uses the same IMAP/SMTP servers; only the UI differs.
Gmail Email Settings for Outlook (Windows & Mac)
Recent versions of Outlook can connect to Gmail via OAuth or manual IMAP/SMTP configuration. To use OAuth, add a new account and select Google; Outlook will open a Google sign‑in window and handle server settings for you.
If you choose manual settings, create a new IMAP account and enter imap.gmail.com on port 993 with SSL/TLS, plus smtp.gmail.com on port 587 with STARTTLS, using your email address as the username and your app password as the password.
Configuring Gmail SMTP & IMAP in Thunderbird

Thunderbird has first‑class Gmail integration and uses OAuth2 for authentication. To connect:
- Open Thunderbird and go to Account Settings → Account Actions → Add Mail Account.
- Enter your name, Gmail address, and password (or app password) and click Continue.
- Choose IMAP (recommended) and Thunderbird will propose the correct servers.
- When prompted, Thunderbird will open a Google window for OAuth; sign in and allow access.
After setup, adjust synchronization and folder mapping as needed for labels and archiving.
Windows Mail Sync via OAuth
On Windows 10/11, the built‑in Mail app can connect to Gmail using Google’s OAuth flow. In Mail, go to Settings → Manage Accounts → Add account → Google, then sign in with your Gmail or Workspace account and allow the requested permissions.
Manual IMAP/SMTP entry is rarely needed; the app uses the correct Gmail servers automatically.
Bluemail OAuth Integration Setup
BlueMail supports Gmail via OAuth on both desktop and mobile. Choose Add Account → Google, then follow the Google sign‑in flow. If you must configure manually, re‑use the IMAP/SMTP details from the summary table and use an app password for authentication.
Gmail Email Settings for eM Client

eM Client offers automatic Gmail configuration via OAuth. Use the setup wizard, select Google, and sign in with your Gmail account; eM Client will configure IMAP and SMTP with the correct servers.
For manual setup, create an IMAP account and specify imap.gmail.com:993 with SSL/TLS and smtp.gmail.com:587 with STARTTLS.
Gmail Email Settings for Mailbird

Mailbird can access Gmail via IMAP/SMTP or via an OAuth‑based “Gmail” profile. Choose Add Account → Gmail for the easiest setup; Mailbird will detect the IMAP/SMTP endpoints automatically.
Manual configuration uses the same IMAP and SMTP servers described earlier; use your full email address and app password if 2FA is enabled.
Gmail Email Settings for Mailspring

Mailspring supports Gmail OAuth. Choose Gmail as the provider in the account wizard and sign in with Google. If manual configuration is required, supply the same IMAP/SMTP servers and authentication details as other clients.
Gmail Email Settings for Postbox

Postbox includes a Gmail profile that automatically configures IMAP and SMTP. When you add a Gmail account, select the Gmail preset and authenticate via Google; Postbox will use imap.gmail.com and smtp.gmail.com with appropriate ports.
Using Gmail SMTP in SendBlaster (With Caution)

SendBlaster can use Gmail’s SMTP for small mailings, but Gmail’s daily sending limits and anti‑abuse checks make it unsuitable for large bulk campaigns. If you choose this route, configure SMTP with smtp.gmail.com, port 465 or 587, and an app password for authentication.
For regular newsletters or high‑volume lists, move to a dedicated ESP or SMTP relay instead of relying on Gmail SMTP.
Connecting Gmail IMAP/SMTP in MailJerry

MailJerry is typically used for migrations and IMAP‑based copying between providers. It connects to Gmail using IMAP settings (imap.gmail.com, port 993, SSL) and your Gmail credentials or app password, then uses the same settings for the target provider.
Gmail Email Settings in Clean.email

Clean.email usually connects to Gmail via OAuth, not manual IMAP settings. When you authorize Clean.email, it uses IMAP under the hood with imap.gmail.com and the standard port, relying on Google tokens rather than storing your password.
Gmail Email Settings on Apple Devices
Gmail Email Settings for Apple Mail/Icloud (macOS)

Apple Mail integrates with Gmail using OAuth for both personal and Workspace accounts. To set it up:
- Open Mail → Add Account.
- Select Google and click Continue.
- Sign in with your Gmail or Workspace address, approve the requested permissions, and ensure the Mail checkbox is selected.
Apple Mail will configure IMAP and SMTP automatically. You can review the underlying servers in the account’s advanced settings; they follow the same imap.gmail.com / smtp.gmail.com pattern.
Gmail Email Settings for iPhone and iPad
On iOS and iPadOS, the simplest route is to add Gmail as a Google account at the OS level:
- Go to Settings → Mail → Accounts → Add Account.
- Tap Google.
- Sign in with your Gmail/Workspace account and grant access.
- Enable Mail (and any other services you want) and tap Save.
The built‑in Mail app will use IMAP and SMTP with OAuth behind the scenes; you do not usually need to enter server details manually.
Gmail Setup on Mobile Devices
Gmail Email Settings on Android (Native Mail Apps)
On Android, the most robust method is to add your Google account at the system level (Settings → Accounts → Add account → Google), which gives Gmail access to all Google services. If you use a third‑party mail app, choose the Gmail/Google option when available to leverage OAuth.
For manual configuration in a generic IMAP client, use imap.gmail.com:993 with SSL/TLS and smtp.gmail.com:587 with STARTTLS, plus your email address and app password for authentication.
Gmail Email Settings in the Gmail App
The Gmail app on Android and iOS does not require manual server configuration for Gmail accounts; it is pre‑configured to talk to Google’s servers. You simply sign in with your Google account and manage sync, notification, and inbox settings inside the app.
You only need IMAP/SMTP details when connecting non‑Gmail accounts into the Gmail app (via “Add another email account”), in which case you follow the other provider’s server settings.
Troubleshooting Gmail Email Settings
Symptom → Likely Cause → Fix
| Symptom | Likely Cause | Check in Gmail | ✅ Check in Client |
|---|---|---|---|
| Repeated password prompts / “invalid credentials” | 2FA enabled but using normal password; OAuth token expired or blocked. | Confirm 2FA status; create app password; review security alerts. | Update stored password to app password; re‑authorize OAuth. |
| Cannot connect to IMAP/POP server | IMAP/POP disabled or wrong port/encryption. | Check Forwarding and POP/IMAP tab; ensure protocol enabled. | Verify server, port (993/995), SSL/TLS settings. |
| Messages stuck in Outbox | Wrong SMTP port/encryption or auth disabled. | No change; SMTP is client‑side. Ensure account not blocked. | Confirm smtp.gmail.com, port 465/587, SSL/STARTTLS, auth enabled. |
| Only some folders/labels sync | IMAP disabled for specific labels; client folder selection. | In Gmail’s Labels settings, enable “Show in IMAP” for needed labels. | Update client sync/folder subscriptions. |
| Gmail security alert / “sign‑in attempt blocked” | New client, region change, or legacy auth method. | Review security alerts; approve sign‑in or generate app password. | Retry connection using OAuth or app password. |
Security / Access Errors
If you see errors about “less secure apps” or blocked sign‑ins, the solution is almost always to move to OAuth‑based connections or to use an app password if the client cannot handle OAuth. After adjusting authentication, clear any stored credentials in the client and re‑enter them so it does not keep retrying with old, blocked details.
Best Practices for Using Gmail with External Clients & Tools
- Use IMAP as your default protocol and avoid POP unless you have a clear archival or one‑device use case.
- Prefer OAuth‑based connections for modern clients; use app passwords for WordPress and legacy tools.
- Treat Gmail’s web interface and server as the source of truth; let clients mirror mail rather than own it.
- Limit the number of concurrently connected devices and avoid overly aggressive polling intervals.
- Do not send bulk campaigns through Gmail SMTP; move recurring newsletters and automation to dedicated ESPs.
FAQ Gmail Email Settings
Do I need both IMAP and POP enabled in Gmail?
No. For most users, enabling IMAP alone is enough. POP is only needed if you have a specific reason to download and possibly delete messages from Gmail on a single device.
Why does Outlook or Apple Mail keep asking for my Gmail password?
This usually happens when 2‑Step Verification is on and the client is using your normal password instead of an app password, or when an OAuth token has expired or been revoked. Generate a new app password or re‑authorize the account via Google’s sign‑in window to fix it.
Can I use Gmail SMTP with my own domain address?
Yes. With Google Workspace, your custom domain mailboxes use the same Gmail SMTP servers. For personal Gmail, you can configure “Send mail as” and sometimes use Gmail SMTP with a custom From, but for serious branded sending you should consider Workspace or a dedicated SMTP/ESP.
Are Gmail email settings different for Workspace vs free Gmail?
The IMAP, POP, and SMTP servers and ports are the same; the main differences are address format (custom domains vs @gmail.com), admin controls, and sending limits. Workspace admins can also enforce policies on which protocols are allowed.
How do I switch from POP to IMAP safely?
Enable IMAP in Gmail, add the account as IMAP in your client, and let it sync before decommissioning the POP profile. Be careful not to delete server copies from the POP account without confirming that IMAP has a full copy.
Is it safe to connect Gmail to WordPress or desktop clients?
Yes, if you use OAuth or app passwords and keep 2‑Step Verification enabled. Avoid storing your main account password directly and regularly review which apps have access in your Google account security settings.
About This Guide
The Gmail email settings on this page were last verified on April 12, 2026 against the provider’s official help documentation, publicly available postmaster resources, and independent user setup reports. Email server configurations rarely change once established, most providers issue major updates only every one to two years, typically tied to phasing out unencrypted protocols or migrating to new mail infrastructure. SMTPedia re-verifies these settings quarterly and after any announced changes from Gmail. If you find a discrepancy between what is documented here and what Gmail currently requires, please report it so we can update the reference.
About the Author

Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
