When configuring Gmail SMTP settings in an email program or a supported app, the outgoing server commonly uses smtp.gmail.com. The two frequently documented secure port combinations are 465 for SSL and 587 for TLS/STARTTLS. Server details are only one part of setup: modern authentication requirements and account policies can prevent a connection even when the host and port are correct.
Editorial icon by OpenMoji, CC BY-SA 4.0; not an official app or game screenshot.
Gmail outgoing SMTP server settings
| Setting | Common value |
|---|---|
| SMTP server | smtp.gmail.com |
| SSL port | 465 |
| TLS/STARTTLS port | 587 |
| Username | Full Gmail email address |
| Authentication | OAuth or an eligible account-supported method |
These values apply to Google’s standard Gmail SMTP endpoint. Google Workspace can offer administrator-controlled relay configurations that are not interchangeable with ordinary consumer Gmail login.
Why a normal Gmail password may fail
Google has moved away from older ‘less secure apps’ password authentication. Supported applications may use OAuth sign-in. In some accounts, a specially generated app password may be available after enabling two-step verification, subject to account settings. Not every Google account offers app passwords, and an organizational administrator may restrict them.
How to troubleshoot an SMTP connection
- Double-check the outgoing host and whether the selected port matches the encryption setting.
- Confirm the account is allowed to sign in through the method used by the application.
- Inspect any specific error message instead of repeatedly changing unrelated settings.
- Check system clock, firewall or network restrictions where relevant.
- Use Google’s official authentication guidance before enabling additional permissions.
Do not disable encryption or give a third-party service your full account password just to bypass an authentication error.
Common SMTP error categories
Authentication rejected
The app may be using an unsupported sign-in method, an incorrect credential or a blocked account policy. An authentication error is different from a socket connection failure.
Connection timed out
Check whether the network allows the chosen outgoing port. Corporate or public networks can block outbound SMTP connections.
Mail sends but does not arrive
Look for spam or rejection details and check whether the destination address is correct. SMTP acceptance by an outgoing server does not guarantee that every recipient will receive or display the message.
SMTP versus IMAP
SMTP is used for sending. IMAP is used to synchronize inbox messages with supported clients. If incoming email is broken but sending works, investigate incoming server settings rather than changing SMTP blindly.
FAQ
What is Gmail’s SMTP hostname?
smtp.gmail.com.
Is port 587 secure?
It is commonly used with STARTTLS, but encryption must be correctly negotiated.
Can every account create an app password?
No, availability varies by account and policy.
Is OAuth generally preferable where supported?
It avoids sharing the main account password directly with an app.
See Google’s email client setup guidance and app password information. For unrelated inbox delivery problems, visit our Gmail troubleshooting page.
