Gmail SMTP Configuration: Your Comprehensive Guide

Gmail SMTP is smtp.gmail.com on port 587 with STARTTLS, or port 465 with SSL, plus your full address and a password or app password.

Written by

Luka Pecavar

Published on

12 min

Gmail SMTP settings are the host smtp.gmail.com, port 587 with TLS (STARTTLS), or port 465 with SSL, plus authentication using your full email address and a password or an app password. Gmail does support SMTP. That is how Outlook, Thunderbird, and other apps send mail through a Gmail or Google Workspace account.

What is SMTP Configuration?

Introduction to SMTP

SMTP, Simple Mail Transfer Protocol, is the conversation a mail client uses to hand a message to a sending server. You choose the host, the port, the encryption, and the credentials. When you press send, the client opens that connection, authenticates, and submits the message. The recipient's server, and any filter in front of the inbox, still decide what happens after that handoff.

How Does Gmail SMTP Work?

A client configured for Gmail connects to smtp.gmail.com. On port 587 it starts plain and upgrades with STARTTLS. On port 465 it uses SSL from the first byte. It then signs in with the full mailbox address and a password or an app password, and only then submits the message. Encryption covers the message on the way to Google. The recipient's filter still scores the message on its own.

Why Configure Gmail SMTP?

Set these values when an app asks for an outgoing server. Outlook and Thunderbird can send as your Gmail or Google Workspace address once the host, port, and password are filled in. A site such as WordPress can use the same fields for mail it generates, including order confirmations and password resets. The messages go out through that Google mailbox, so Google's sending cap for the mailbox still applies. The settings let the app authenticate. Inbox placement still depends on the content, the list, and the mailbox you send from.

Gmail SMTP Server Settings

Enter the values below in the client's outgoing-mail screen, turn authentication on, save, and send a test to yourself. If the test fails, use the troubleshooting section further down before you change anything else.

Gmail SMTP Settings

Essential Gmail SMTP Server Details

The client needs three things: where to connect, which port and encryption to use, and which mailbox is sending.

  • SMTP Server Address: smtp.gmail.com. This host accepts the outgoing connection for Gmail and Google Workspace mailboxes.

  • SMTP Port: Use port 587 with TLS (STARTTLS) when the client lists it. Use port 465 with SSL when the client only offers SSL, or when 587 fails. Match the encryption mode to the port you typed.

  • Authentication: Turn authentication on. The username is the full mailbox address, a @gmail.com address or a Google Workspace address. The password is the account password, or an app password when 2-step verification is on.

A working setup is smtp.gmail.com, port 587 or 465 with the matching encryption, and authentication with that mailbox. The table is the same list in one place.

SettingValue
SMTP serversmtp.gmail.com
Port and encryption587 with TLS (STARTTLS)
Alternate port465 with SSL
UsernameFull Gmail or Google Workspace address
PasswordAccount password, or an app password if 2FA is on
AuthenticationRequired

Understanding Port Selection and Security

Port 587 and port 465 both encrypt the session. They start it differently. Port 587 connects and then upgrades to TLS (STARTTLS). Port 465 encrypts with SSL from the start. Try 587 with STARTTLS first when the client offers that choice. If the client only offers SSL, use 465. A port that does not match the encryption mode is a common reason the client times out or drops the login.

Why these Specific Settings?

Each field does one job. The host tells the client which server to open. The port and encryption tell it how to protect the session. Authentication tells Google which mailbox is submitting the mail. A wrong host fails the connection. A wrong port or encryption mode stalls or resets it. A wrong password fails the login. The next section is where you turn those protections on.

Security and Authentication

Save the account only after authentication is on and the port matches TLS or SSL. Those two checks are what keep the password and the message encrypted between the client and smtp.gmail.com.

Understanding Authentication

Authentication is Google checking the mailbox address and the secret you typed before it accepts a message. Turn it on and use the full address as the username, including the domain.

Two-Factor Authentication and App Passwords

Turn on 2-step verification for the Google account, then give the mail client an app password. Many desktop and web clients have a single password field and no place to type a phone code. An app password is a separate secret for that app. You paste it into the SMTP password field. The account password stays out of the client. Revoke the app password when you stop using the app.

TLS and SSL Encryption: Ensuring Secure Transmission

TLS and SSL encrypt the session so the password and the message body are not readable on the network between you and Google. Gmail uses TLS, including STARTTLS on port 587, and SSL on port 465. Use STARTTLS on 587 when the client offers it. Encryption covers the trip to Google's server. It leaves the recipient's spam scoring alone.

Why Security is Paramount in Gmail SMTP Configuration

The SMTP password is enough to send as that mailbox. Encryption keeps that secret, and anything in the message, private on the way to Google. Google receives the message once the session is accepted. The recipient's provider applies its own filters after that. Use a current app password, revoke ones you no longer need, and keep the account's 2-step verification on.

App Password Generation

Create an app password when the client cannot complete 2-step verification. You generate it in the Google account, paste it into that one client, and revoke it from the same page when the client is retired.

Generating an App Password

Step-by-Step Guide to Creating an App Password

The Google Account security page is where the password is issued:

  • Access your Google Account: Sign in and open the Security section.

  • Navigate to App Passwords: Open App passwords. It may sit under Signing in to Google. The page appears for accounts that already use 2-step verification.

  • Select the App and Device: Choose the app that will use Gmail SMTP, and the device you are on, if Google asks for both.

  • Generate the App Password: Click Generate. Google shows an app password. Copy it and treat it with the same care as the account password.

  • Use the App Password: Paste it into the password field of the client's SMTP settings. Leave the username as the full mailbox address.

Managing and Revoking App Passwords

After the client can send, revoke app passwords you no longer use. The same cleanup belongs with any IMAP and SMTP setup you retire.

  • Reviewing Existing App Passwords: The App passwords section lists the ones you have generated, with the app and device name you chose.

  • Revoking App Passwords: Click Revoke next to a password you no longer want. That app loses access on the next connection. Create a new app password if you still need the client.

Revoking is the way you take SMTP access back without changing the Google account password. Check the list when a laptop is lost or a site you used for sending is shut down.

Troubleshooting Common Issues

Troubleshooting Gmail SMTP

When a test message fails, check authentication first, then the host and port, then whether the mailbox has hit its sending cap. Work in that order so you change one setting at a time.

Authentication Errors

The client rejects the login when the username or password does not match. Retype the full mailbox address, including @gmail.com or your Google Workspace domain. If 2-step verification is on, paste an app password into the password field.

Connection Timeouts

A timeout means the client never completed the session with smtp.gmail.com. Confirm the network can reach the internet. Confirm a firewall allows outbound connections on port 587 or 465, matching the port you set. Then recheck the host name and that TLS or SSL matches that port.

Emails Marked as Spam

A correct SMTP setup can still land in spam. Filters react to the content, the links, and the sending pattern. Heavy promotional language and a sudden jump in volume from a new mailbox are common triggers. Edit the copy and raise volume gradually. What filters tend to react to is covered in cold email vs spam.

Warmup is a separate practice from the host and port. The SMTP settings stay the same while you warm the mailbox. The steps for that process are in the email warmup guide.

Sending Limits Exceeded

Gmail and Google Workspace cap sending so a mailbox is not an open relay. Past the cap, sending can pause until the window resets. For Workspace, Google's help page Gmail sending limits in Google Workspace lists 2,000 messages per day on a paid account and 500 messages per day on a free trial. The Workspace sending limits guide keeps the rest of that table. A consumer @gmail.com inbox uses Google's consumer limits. The 500 figure above is the Workspace trial, so look up the current consumer page before you plan volume for a personal inbox. Spread sends across days or more mailboxes when you need more room. The host and port stay the ones in the table. The Gmail sending limit guide covers how those caps behave in practice.

Incorrect Port or Security Settings

Use port 587 with STARTTLS when the client offers it. Use port 465 with SSL if 587 fails or the app only lists SSL. Turn the matching encryption on in the client. A mismatch here shows up as a timeout or a failed login, which the sections above already walk through. After you change the port, send one test to yourself.

Change one setting, send one test, and read the client error before you change the next setting.

Best Practices

Retest the account after you change a password, a port, or a Google sign-in setting. A test to your own inbox tells you the session works before a real recipient is involved.

Regular Testing and Monitoring

Send a short test after any settings change. Watch bounces and login errors in the client. A sudden rise in bounces points at bad addresses. A sudden rise in authentication errors points at the password or the username.

Staying Updated with Gmail’s Changes

Google changes sign-in rules and which clients may use an app password. When a client that worked yesterday starts failing login, recheck Security and App passwords before you edit the host. Follow Google's own account announcements for those changes.

Maintaining a Clean Email List

Remove addresses that bounce or that you know are unused. That cuts repeated bounces from bad data. A verification pass can flag addresses that are already invalid so you drop them before the next send.

Adhering to Sending Best Practices

Write to people the message is for. Skip stacked promotional lines and surprise links. Split the list into groups that share a reason to hear from you, and keep the first sends from a new mailbox small. The SMTP fields stay the same while you do that.

The configuration is the host, the port, the encryption, and the password. Recheck those four when sending breaks. Recheck the copy and the list when mail is refused or filed as spam.

If you send cold email from a mailbox that uses these Gmail SMTP settings, the host, port, and password still come from Google. Manyreach is a cold email platform with sequences, warmup, a unified inbox, and CRM. Every plan, including Pay As You Go, includes unlimited sending accounts and unlimited prospects. Signup includes 250 free sending credits, and no credit card is required. The daily cap stays the one Google sets for that mailbox. Visit Manyreach when you want the campaign tools, and use this page when you connect the mailbox.

FAQs

What are the Gmail SMTP settings?

Use host smtp.gmail.com. Choose port 587 with TLS or STARTTLS, or port 465 with SSL. The username is the full mailbox address, whether it ends in @gmail.com or a Google Workspace domain. Configuracion SMTP Gmail is this same setup. The password is your Google password, or an app password when 2-step verification is on.

Does Gmail use SMTP?

Yes. Gmail and Google Workspace accept SMTP on smtp.gmail.com for outgoing mail. You still turn authentication on. Reading mail is usually IMAP or POP, which is separate from these send settings. Gmail does support SMTP.

Should I use port 587 or port 465?

Use 587 with STARTTLS when the client offers it. Use 465 with SSL if 587 fails or the app only lists SSL. Match the encryption to the port. A mismatch is a common reason the client times out or refuses the login.

How do I allow or activate SMTP in Gmail?

There is no separate SMTP on/off switch for a normal Gmail account. You allow a client by signing in with the full address and, when 2-step verification is on, an app password from the Google Account security page. If the client says the connection to the outgoing server smtp.gmail.com failed, recheck the host, the port, and that outgoing authentication is enabled.

What does a Gmail relay denied error mean?

If the client reports relaying denied, relay not permitted, or relay access denied for smtp.gmail.com, Google refused the send. Recheck authentication, use the full mailbox address as the username, use an app password when 2FA is on, and send from that same mailbox. A wrong port shows up more often as a connection failure, covered above.

Luka Pecavar

About the author

Luka Pecavar

Share Article

The Only Truly ‘Unlimited’ Cold Emailing Platform

Manyreach lets you connect unlimited mailboxes to send cold emails to unlimited contacts & add unlimited team members under unlimited workspaces.

Start for free now