Gmail SMTP Configuration
Use these exact values when configuring any email client or application to send through Gmail's servers.
| Parameter | Value |
|---|---|
| SMTP Host | smtp.gmail.com |
| SMTP Port | 587 (TLS) or 465 (SSL) |
| Encryption | STARTTLS on port 587, SSL on port 465 |
| Username | Your full Gmail address |
| Authentication | App Password (not your account password) |
Important: Gmail requires an App Password for SMTP access. Your regular account password will not work. You must enable 2-Step Verification on your Google Account before you can generate App Passwords.
Step-by-Step Setup
Follow these steps in order to enable SMTP access for your Gmail account.
1. Enable 2-Step Verification
Navigate to your Google Account, select Security, and turn on 2-Step Verification using your phone number or authenticator app.
2. Generate an App Password
Visit myaccount.google.com/app-passwords while signed in. Select "Mail" as the app and choose "Other (Custom name)" for the device.
3. Configure Your Application
Enter smtp.gmail.com as the SMTP host, port 587 with TLS enabled, your full Gmail address as the username, and the App Password as the credential.
4. Send a Test Message
Verify the configuration by sending an email to yourself. Check your sent folder in Gmail web to confirm the message was sent through the configured application.
Common Errors and Solutions
Most Gmail SMTP issues fall into a handful of categories. Here's how to fix them quickly.
Authentication Failed
Using your regular password instead of an App Password is the most common cause. Google blocks normal password authentication for SMTP. Generate a fresh App Password and ensure you paste it without any spaces.
Connection Timeout
Port 587 is sometimes blocked by corporate firewalls or restrictive networks. Switch to port 465 with SSL encryption as an alternative.
Less Secure App Access Denied
Google deprecated this feature in 2022. The only supported method now is App Passwords with 2-Step Verification.
Daily Sending Limit Reached
Gmail limits regular accounts to 500 emails per day and Google Workspace accounts to 2,000. For higher volume, consider dedicated email infrastructure.
Best Practices for Gmail SMTP
Keep your account secure and your messages deliverable with these recommended approaches.
Use App Passwords Exclusively
Never share your actual Google password with any third-party application. App Passwords isolate access and can be revoked individually.
Rotate App Passwords Periodically
If you suspect compromise, revoke old App Passwords and generate new ones from your Google Account security settings.
Monitor Sending Reputation
Gmail's filters are aggressive. Avoid sudden volume spikes and ensure your content doesn't trigger spam signals.
Separate Personal and Application Email
Use a dedicated Gmail account for application sending to protect your primary account's reputation.
When Gmail SMTP Falls Short
Gmail's SMTP service works for low-volume personal use, but production applications with high-frequency sending quickly hit constraints. Gmail imposes strict rate limits, offers no deliverability analytics, and provides no bounce handling. A dedicated email API gives you webhooks, detailed logs, and infrastructure built for deliverability at scale.
For teams sending across multiple domains or needing intelligent routing rules, a SMTP relay service prevents your messages from being flagged as suspicious. Learn more about improving email deliverability through correct authentication setup.
For cold outreach or new sender addresses, an email warmup strategy gradually builds your sender reputation instead of triggering spam flags with sudden high-volume bursts.
Frequently Asked Questions
What is the difference between port 587 and port 465?
Port 587 uses STARTTLS, which upgrades an unencrypted connection to TLS. Port 465 uses implicit SSL/TLS from the start of the connection. Both are secure, but port 587 is more widely supported and is the recommended submission port.
Why do I need an App Password instead of my regular password?
Google blocks password-based authentication for third-party apps to protect your account. App Passwords are scoped to specific applications and can be revoked individually without affecting your main account password or access to your Google Account.
Can I use Gmail SMTP for bulk email marketing?
No. Gmail's daily sending limit of 500 emails for personal accounts (2,000 for Google Workspace) makes it unsuitable for bulk email. For marketing campaigns or high-volume transactional email, use a dedicated email service with proper infrastructure.
How do I increase my Gmail sending limit?
Google Workspace accounts have a 2,000 email per day limit. There is no way to increase this further for personal Gmail accounts. For higher volume needs, migrate to a dedicated email service provider that offers scalable infrastructure.
What happens if I exceed Gmail's sending limit?
When you exceed the daily limit, Gmail will reject further sending attempts with a "Daily sending limit exceeded" error. The limit resets at midnight Pacific Time. If you consistently hit the limit, you need a dedicated email solution.
Ready to move to reliable email infrastructure?
Start free with no card, or talk to sales for high-volume and enterprise.
Start SendingTalk to Sales