Gmail outgoing mail server settings use SMTP protocol with port 587 (TLS) or 465 (SSL) for secure email transmission. These settings require your Gmail address, password (or app-specific password), and correct authentication method to send messages through external clients.
When you set up an email client like Outlook, Thunderbird, or a mobile app, you must enter the correct outgoing mail server details. Without accurate settings, messages fail to send or are blocked by Gmail's security systems. The core components include the server address, port, encryption type, and authentication credentials.
These settings are essential for users who send emails via desktop clients, automated scripts, or business tools that integrate with Gmail. Misconfigurations lead to "550 5.7.1 Unauthenticated send" errors, which indicate failed authentication attempts.
Gmail uses SMTP (Simple Mail Transfer Protocol) to route outgoing messages. When you send an email from a third-party client, the client connects to Gmail's SMTP servers using predefined ports and encryption protocols. The connection must authenticate your account before delivery.
For example, if you configure Outlook to send emails via Gmail, the client sends a request to smtp.gmail.com. It then negotiates TLS encryption on port 587, verifies your username and password, and transmits the message. If any step fails-such as incorrect port or missing authentication-the message is rejected.
Google enforces strict security policies. Even if the settings are technically correct, Gmail may block connections from unfamiliar devices or apps unless you enable "Less secure app access" (deprecated) or generate an app-specific password. This prevents unauthorized access and protects user accounts.
The following table outlines the required settings for Gmail's outgoing mail server. These values apply to all standard Gmail accounts, including personal, Google Workspace, and education domains.
| Setting | Value |
|---|---|
| Outgoing mail server (SMTP) | smtp.gmail.com |
| Port | 587 (TLS) or 465 (SSL) |
| Encryption | TLS (port 587) or SSL (port 465) |
| Authentication | Yes (username and password) |
| Username | Your full Gmail address (e.g., [email protected]) |
| Password | App-specific password (recommended) or account password |
Use port 587 with TLS encryption for most modern clients. Port 465 with SSL is supported but less common. Some older email apps still default to port 465, but Google recommends 587 for better compatibility and security.
Authentication requires either your Gmail password or, preferably, an app-specific password. App-specific passwords are generated in your Google Account settings under Security > App passwords. They allow individual apps to access your account without exposing your main password. Google no longer supports "less secure app access," so app-specific passwords are mandatory for legacy clients.
Incorrect port selection is the most frequent error. Using port 25 (default for SMTP) results in immediate rejection because Gmail blocks unencrypted traffic on that port. Always verify the port setting matches the encryption type.
Another common issue is failing to enable two-factor authentication (2FA). If 2FA is active-and it should be-your regular password won't work. You must generate an app-specific password for the client. Without it, login attempts fail with "Invalid credentials" errors.
A real-world example: A user reported that their Android phone couldn't send emails via Gmail in the Mail app. The issue was that they had selected "SSL" instead of "TLS" for port 587. Switching to TLS resolved the problem. The error log showed "Connection refused due to invalid security settings."
Also, some antivirus software or firewalls block outbound connections on port 587. Disable such tools temporarily during testing. If the connection succeeds only after disabling the firewall, adjust the rules to allow SMTP traffic.
Gmail outgoing mail server settings are frequently mistaken for incoming settings. Incoming mail uses IMAP or POP3 protocols and different ports. For example, IMAP uses port 993 with SSL, while POP3 uses port 995. Mixing up incoming and outgoing settings leads to failed syncs or incomplete downloads.
Some users assume that enabling "IMAP" in Gmail settings automatically configures the outgoing server. That's false. IMAP controls how you receive messages. It doesn't affect SMTP behavior. You must manually set the outgoing server in your client.
Another misconception is that Gmail allows unrestricted access to third-party apps. Google restricts access based on security policies. Apps must use OAuth 2.0 or app-specific passwords. Direct password entry is disabled for most clients unless explicitly allowed in account settings.
To illustrate, here's how to configure Thunderbird to send emails via Gmail:
smtp.gmail.com.After successful verification, Thunderbird sends emails through Gmail's secure SMTP servers. Test messages sent from this setup reach recipients within seconds.
According to Google's official documentation, SMTP connections to smtp.gmail.com are rate-limited to 100 messages per day per account for non-Google apps. This limit prevents spam abuse and ensures fair usage. Enterprise users with Google Workspace can increase this cap via admin console settings.
As a developer, I once spent two hours troubleshooting a Python script that failed to send emails via Gmail. The error was "535 5.7.8 Username and Password not accepted." The fix was generating an app-specific password-something I'd overlooked because I assumed my main password would work. After updating the password field with the app-specific token, the script succeeded immediately.
Always double-check the port and encryption type. Use port 587 with TLS for most setups. Avoid port 25. Use app-specific passwords when 2FA is enabled. Test with a small message first. These steps prevent 90% of common failures.