Gmail SMTP Server Address, Ports and Settings

To send mail through your Gmail account from an email client like Outlook, a WordPress plugin or a website contact form, the app needs Gmail's SMTP server settings.

The Gmail SMTP server address is smtp.gmail.com. You also need the right port, encryption setting and login method. This guide lists all of them and explains the errors you get when one is wrong.

Gmail SMTP Settings: Quick Reference

These settings work for personal Gmail accounts and for Google Workspace accounts.

Gmail SMTP Server Configuration Details

Source: Google's IMAP, POP and SMTP documentation. A wrong port or encryption setting is the most common reason a connection fails, so copy these values exactly. For what happens after your mail leaves Gmail, see our email deliverability best practices.

How Does the Gmail SMTP Server Actually Work?

SMTP (Simple Mail Transfer Protocol) is the protocol email clients and servers use to send mail. smtp.gmail.com is the server that accepts outgoing mail from your Google account.

When you click "send" in Outlook or a web app, the message does not go straight to the recipient. Your app connects to smtp.gmail.com, logs in and hands over the message, and Gmail delivers it.

The Authentication and Relay Journey

The server first checks your username and password (or OAuth token), so only you can send from your address. The connection is encrypted with TLS. Once you are logged in, Gmail accepts the message, applies its sending limits and delivers it to the recipient's server. Messages sent this way appear in your Gmail "Sent" folder, like mail sent from the web interface.

Configuring SMTP Ports and Security Options

smtp.gmail.com only accepts encrypted connections. You have two ports; pick the one your app supports.

Port 587 With TLS and STARTTLS

On port 587 the app connects in plain text and then issues the STARTTLS command, which upgrades the connection to TLS (Transport Layer Security) before any login details or message content are sent. Most apps label this setting "TLS" or "STARTTLS".

Port 465 With SSL

On port 465 the connection is encrypted from the first byte ("implicit TLS", often labeled "SSL" in apps). It is not outdated: RFC 8314 recommends implicit TLS for mail submission and says both methods are equally secure when implemented correctly (RFC 8314). Use whichever your app supports.

The most common SMTP problems fall into three groups:

Each group has its own fix, covered in the troubleshooting section below.

Using App Passwords for Secure Authentication

Apps that support "Sign in with Google" connect with OAuth, and Google recommends that option. For apps that only accept a username and password, create an App Password: a 16-character passcode that lets one app use your account without your main password (Google Account Help).

How to Generate an App Password

App Passwords require 2-Step Verification (2SV) on your Google Account. Then:

1. Go to myaccount.google.com/apppasswords and sign in.

2. Enter a name for the app (for example, "WordPress").

3. Click Create to get the 16-character password.

Security Tip: Copy the password into your app right away. Google shows it only once.

Enter it in the app's SMTP password field. You can revoke it later from the same page without affecting other apps. The option is missing if your account uses 2SV with security keys only, is enrolled in Advanced Protection, or is a work or school account where your administrator has not allowed it.

Gmail SMTP Sending Limits

Gmail's SMTP server is fine for notifications, contact forms and personal mail. It is not built for bulk sending, and Google enforces limits.

A personal Gmail account can send about 500 emails per day. Go over it and Gmail blocks sending; you can usually send again within 1 to 24 hours (Gmail Help).

Understanding the Limits

The daily count is not the only limit. A single message to more than 500 recipients also triggers the block.

Google Workspace accounts have higher limits: 2,000 messages per day per user (500 during a trial), 10,000 total recipients per day, 3,000 external recipients per day (addresses outside your primary domain), and 100 recipients per message when you send through SMTP (Google Workspace Admin Help: Gmail sending limits in Google Workspace, page updated September 24, 2026, checked September 2026). Exceeding them suspends sending for up to 24 hours.

Strategic Alternatives for Bulk Sending

If you need to send more than these limits allow, do not work around them with more Gmail accounts. Use a tool built for the job:

• Google Groups: send one message to a group address for internal updates to a known list of members.

• Google Workspace: higher limits (2,000 messages per user per day) for regular business mail.

• Dedicated Email Platforms: use an email service provider such as Mailchimp or SendGrid for newsletters and other bulk mail.

For more on inbox placement, see our guide on email deliverability best practices.

Troubleshooting Gmail SMTP Errors

Most failures come from wrong credentials, a blocked port or a mismatch between port and encryption.

Authentication Failures

An "authentication failed" error means Google rejected your login. Check:

• App Password: with 2-Step Verification on, your regular password does not work in apps without Google sign-in. Use the 16-character App Password, without spaces.

• Full Email as Username: the username is your full address, such as you@gmail.com.

• 'Less Secure App Access': this setting no longer exists. Use an App Password or Google sign-in.

Connection Timeouts and SSL Errors

If the login details are right and the connection still fails, the problem is the network or the encryption setting. A "connection timeout" means your app cannot reach smtp.gmail.com at all: something between you and Google blocks the port. Some hosting providers and networks block outgoing SMTP ports.

To resolve connection blocks:

1. Firewall and Antivirus: these can block ports 465 and 587 without telling you. Turn them off briefly to test. If the connection then works, add an exception for your email app.

2. Port and Encryption: port 587 needs TLS/STARTTLS; port 465 needs SSL. Any other combination fails.

Note: An "SSL handshake failed" error means the port and encryption setting do not match. Switch to one of the two pairs above.

Gmail SMTP FAQ: Quick Answers to Common Questions

Can I Use the Gmail SMTP Server for Business for Free?

A free Gmail account can send about 500 emails per day. That covers light business mail and contact forms. Above it, Gmail blocks sending for up to 24 hours. For more, use a Google Workspace account (2,000 messages per day) or a dedicated email service.

Why Is My SMTP Connection Getting Refused?

A "connection refused" error from smtp.gmail.com usually has one of three causes:

• Port settings: use 587 for TLS or 465 for SSL.

• Firewall restrictions: a firewall or your hosting provider blocks the port.

• Wrong password: with 2-Step Verification on, your regular password does not work; use an App Password.

Are the SMTP Settings Different for Google Workspace?

The server settings are the same: smtp.gmail.com, the same ports, the same encryption. The differences are the username (your address on your own domain, like you@yourbusiness.com) and the higher sending limits. On work accounts, whether you can use App Passwords and IMAP/SMTP depends on your administrator's settings. To route mail between Workspace accounts instead, see Google Workspace email forwarding. If you use Workspace mailboxes for outreach, warm them up first; see our comparison of email warm-up tools.