Free Gmail accounts and Google Workspace accounts use the same servers. What differs is who controls access: in Workspace, the admin decides whether IMAP and app passwords are allowed. New to the terms? Read what SMTP is first.
Gmail and Google Workspace SMTP, IMAP and POP settings
| Setting | Value |
|---|---|
| Outgoing server (SMTP) | smtp.gmail.com |
| SMTP port and encryption | 587 with TLS (STARTTLS), or 465 with SSL |
| Incoming server (IMAP) | imap.gmail.com |
| IMAP port and encryption | 993, SSL |
| Incoming server (POP) | pop.gmail.com |
| POP port and encryption | 995, SSL |
| Username | The full email address |
| Password | Sign in with Google (OAuth), or a 16-character app password |
These match Google’s own setup guide. For more on 587 versus 465, see SMTP and IMAP ports.
Sign-in: OAuth and app passwords
Since May 1, 2025, Google Workspace no longer allows less secure apps: apps that sign in with only a username and password. Two ways remain:
- Sign in with Google (OAuth). The app opens a Google sign-in window and never sees your password. Current versions of Outlook, Apple Mail and every major cold email tool support it. Use this whenever the app offers it.
- App password. A separate 16-character password for one app, for tools that can only take a password. It needs 2-Step Verification on the account.
To create an app password:
- Sign in to the account and open myaccount.google.com, then Security.
- Turn on 2-Step Verification. You can choose an authenticator app instead of a phone number, and one authenticator app can hold many accounts.
- Go to myaccount.google.com/apppasswords, name the app and click Create.
- Copy the 16 characters without the spaces into the app’s password field.
Turning on IMAP in Google Workspace
In a Workspace organization, the admin controls IMAP for everyone. If an app cannot connect at all, check the Admin console under Apps, Google Workspace, Gmail, End User Access, and make sure POP and IMAP access is allowed for the users who need it. In personal Gmail accounts IMAP is always on, so there is no switch to look for.
SMTP relay for apps and devices
Workspace also offers an SMTP relay service at smtp-relay.gmail.com for printers, scanners and in-house apps that need to send through your domain. It is set up in the Admin console under Gmail routing, with your office IP addresses or SMTP sign-in as proof. See Google’s SMTP relay guide. It is not meant for cold email: sending tools connect each inbox directly instead.
Connecting Google inboxes to Instantly, Smartlead or another sending tool
- Sign in with Google, one inbox at a time. In the sending tool, add an account, choose Google or Gmail and sign in. No app password and no 2-Step Verification needed. Some tools first ask the Workspace admin to allow their app in the Admin console under Security, Access and data control, API controls.
- Bulk import with a CSV. Faster for many inboxes, but the CSV connects over IMAP and SMTP, so every inbox needs an app password, and with it 2-Step Verification.
Most teams use the first option. If you order inboxes from us and invite us to your sending tool, we connect them this way for you.
Gmail and Google Workspace sending limits
Google’s Workspace limits allow up to 2,000 messages a day per user, and 500 a day on trial accounts. Free Gmail accounts are limited to about 500. For cold email, stay far below that: 25 to 30 emails per inbox a day after a full warm-up, spread across several inboxes and domains. Our inbox calculator works out how many you need.
Common Gmail SMTP errors and fixes
| Error | What it means | Fix |
|---|---|---|
534-5.7.9 Application-specific password required | 2-Step Verification is on, so a normal password is refused | Create an app password, or use Sign in with Google |
535-5.7.8 Username and Password not accepted | Wrong password, or a normal password where an app password is needed | Check the address and password, or switch to an app password or OAuth |
534-5.7.14 Please log in with your web browser | Google blocked the sign-in as unusual | Sign in once at mail.google.com from the same network, then retry with OAuth |
550-5.4.5 Daily user sending limit exceeded | The account hit its daily limit | Wait up to 24 hours, and lower the daily volume per inbox |
| Connection timed out | The port is blocked on your network | Try 465 instead of 587, or the other way round |
Frequently asked questions
What is the Gmail SMTP server?
smtp.gmail.com, on port 587 with TLS (STARTTLS) or port 465 with SSL. The same server is used by free Gmail accounts and Google Workspace accounts.
What is the Gmail IMAP server?
imap.gmail.com on port 993 with SSL. POP uses pop.gmail.com on port 995 with SSL.
Can I still use my Gmail password in an email app?
Not on its own. Since May 1, 2025, Google Workspace accounts no longer allow apps that sign in with just a username and password. Use an app that supports Sign in with Google (OAuth), or an app password, which needs 2-Step Verification.
Do I need 2-Step Verification for an app password?
Yes. App passwords only appear once 2-Step Verification is on, and turning 2-Step Verification off deletes them. It can be set up with an authenticator app instead of a phone number.
How many emails can a Google Workspace account send a day?
Up to 2,000 messages a day per user, or 500 for trial accounts. For cold email, keep each inbox to 25 to 30 a day after warm-up.
Should I use port 587 or 465 for Gmail?
Either works. 587 starts unencrypted and upgrades with STARTTLS; 465 is encrypted from the first byte. If one is blocked on your network, try the other.