Skip to main content
Skip to content
Gmail setup

How to connect Gmail by SMTP, with an App Password

For when Sign in with Google will not finish, your Workspace admin has turned it off, or you would simply rather not grant OAuth access. An App Password does the same job over SMTP, the same protocol every desktop email client has used for twenty years. Takes about 5 minutes.

In short

1

Turn on 2-Step Verification on the Google account, if it is not on already.

2

Create an App Password at myaccount.google.com/apppasswords.

3

In EmailQo, add a new SMTP sender using the Gmail address, smtp.gmail.com, port 587, and the App Password in place of the regular password.

When to use this instead of Sign in with Google

EmailQo can connect a Gmail account two ways: one click with Sign in with Google (OAuth), or SMTP with an App Password. Most people use Sign in with Google and never read this page. Use the SMTP method below instead when any of these apply:

Sign in with Google is not working

The Google sign-in popup fails, loops, or closes without finishing
Google shows "This app is blocked" or a similar warning
A browser extension or strict privacy setting is blocking the popup

OAuth is disabled for this account

A Google Workspace admin has turned off third-party app access
The account is on Advanced Protection, which disables most OAuth app access
You would rather not grant an app ongoing account access at all
1

STEP 1 OF 3

Turn on 2-Step Verification

Google only offers App Passwords on accounts that have 2-Step Verification turned on. This is a Google requirement, not an EmailQo one, there is no way around it.

1

Go to your Google Account security page myaccount.google.com/security

2

Find 2-Step Verification. If it already says On, skip ahead to step 2.

3

If it says Off, click it, then click Get started.

4

Follow Google's prompts to confirm it is you, usually a code sent to your phone.

5

Click Turn on. 2-Step Verification is now active on the account.

Important

If 2-Step Verification is set up with only a physical security key and no other method, Google sometimes hides the App Passwords option entirely. Adding a phone prompt or an authenticator app as a second method, alongside the key, usually brings it back.

2

STEP 2 OF 3

Create an App Password

An App Password is a 16-character code that works only for the one app it is created for. It cannot sign in to the Google account itself, and it can be revoked at any time without changing the main account password.

1

Go to Google App Passwords myaccount.google.com/apppasswords

2

Sign in again if Google asks for it.

3

In the App name box, type something you will recognize later, such as EmailQo.

4

Click Create.

5

Google shows a 16-character password once, in four groups of four letters, for example abcd efgh ijkl mnop.

6

Copy it now. The spaces do not matter and can be left in or taken out.

7

Click Done.

myaccount.google.com/apppasswords
App passwords
App passwords let you sign in to your Google Account from apps that do not support 2-Step Verification.
App name
EmailQo
Create
Your app password: abcd efgh ijkl mnop. Copy this password and use it in EmailQo.
Type EmailQo and click Create
Note

Do not see an App name box, only a list of existing apps and devices? Scroll past any existing entries, the "Create" option with the name field is further down the same page.

3

STEP 3 OF 3

Add Gmail as a sender in EmailQo

In EmailQo, go to Email Accounts in the sidebar, click Add Sender, choose SMTP, and fill in:

Your NameJohn Smith

What recipients see as the sender name

Email Addressjohn@gmail.com

The full Gmail or Google Workspace address

SMTP Hostsmtp.gmail.com
Port587
Passwordabcdefghijklmnop

The 16-character App Password from step 2, not the regular Gmail password

EmailQo: Add Sender (Gmail)
Add a new email sender: SMTP
Your name
John Smith
Email address
john@gmail.com
SMTP host
smtp.gmail.com
Port
587
Password
abcdefghijklmnop
Save Sender
Paste the 16-character App Password, not your regular Gmail password
You are done.

Gmail free accounts can send up to 500 emails a day, Google Workspace up to 2,000. EmailQo sets a conservative default limit on a new sender, raise it in Email Accounts if needed.

Troubleshooting

Sign in with Google will not finish or keeps failing

This is exactly what the App Password method above is for, it does not depend on the Google sign-in popup at all. Follow the three steps above instead of retrying Sign in with Google.

Authentication failed, wrong username or password

Almost always this means the regular Gmail password was entered instead of the App Password. Go back to myaccount.google.com/apppasswords, create one specifically for EmailQo, and paste that 16-character password instead.

I do not see App Passwords as an option at all

First, confirm 2-Step Verification is fully turned on at myaccount.google.com/security, App Passwords stay hidden until it is. If it is on and the account is through a company or school (Google Workspace), the admin may have disabled App Passwords organization-wide, ask them to allow it, or use a personal Gmail address instead.

My organization disabled less secure app access or App Passwords

A Google Workspace admin controls this under Admin console, Security, Authentication, App passwords. Share this exact path with the admin and ask them to allow App Passwords for the account, or for the whole organization if others need the same thing.

Connection timed out

Try port 465 instead of 587 in EmailQo's sender settings. Some office or hotel networks block port 587 specifically. If neither port connects, the network itself may be blocking outbound SMTP.

Emails send fine but land in spam

This is a deliverability issue, not a connection one, and SMTP sending from a shared Google IP has lower reach than a dedicated sending domain. Turning on warmup in EmailQo and keeping send volume modest helps. For serious volume, Amazon SES with your own domain gives far more control, see the main setup guide.

Common questions

Why would I connect Gmail by SMTP instead of Sign in with Google?

Sign in with Google uses OAuth, which some Google Workspace admins turn off for third-party apps, and which occasionally fails to complete for reasons outside an app's control. An App Password does the same job over SMTP, the protocol every email client has used for decades, so it works even when OAuth sign-in does not.

Is a Gmail App Password safe to use?

Yes. An App Password only works for the one app it was created for, it cannot be used to sign in to the Google account itself, and it can be revoked at any time from myaccount.google.com/apppasswords without affecting the main account password.

Can I use my regular Gmail password instead?

No. Google blocks regular passwords for SMTP access as a security measure. An App Password is required, and it only becomes available once 2-Step Verification is turned on.

I turned on 2-Step Verification but I still do not see App Passwords. Why?

Two common causes. First, if 2-Step Verification is set up only with a physical security key and no other method, Google sometimes hides App Passwords, adding a phone prompt or authenticator app as a second method usually brings the option back. Second, if the account is a Google Workspace account managed by an employer or school, the admin may have turned App Passwords off organization-wide. In that case, ask the admin to allow App Passwords, or use a personal Gmail address instead.

How many emails can I send per day through Gmail SMTP?

Google caps free Gmail accounts at roughly 500 sends a day and Google Workspace accounts at roughly 2,000. EmailQo sets a conservative default limit on new senders and that can be raised in Email Accounts settings, but it will never exceed what Google itself allows.

What is the difference between this and Google Sign-In in EmailQo?

Both end up sending through the same Gmail account. Sign in with Google uses OAuth and does not need an App Password, but it needs Google's sign-in flow to complete and needs third-party access allowed on the account. SMTP with an App Password is the fallback: it needs one extra step to set up, but does not depend on OAuth working at all.

Setting up Microsoft 365 or Outlook instead? There is a dedicated guide for that too.

Outlook setup guide

Ready to connect an account and send your first campaign?

Start free trial

Looking for Amazon SES, Outlook, or the full setup guide? See all setup docs.