Back to HomeGoogle Workspace

Google Workspace SMTP Setup Complete Tutorial: Server Settings, Sending Limits & Troubleshooting

9 min min read
#Google Workspace#SMTP#Email Setup#SMTP Relay#WordPress#Sending Settings#Technical Tutorial#Troubleshooting#Mail Server#Integration

Google Workspace SMTP Setup Complete Tutorial: Server Settings, Sending Limits & Troubleshooting

"My website needs to send notification emails, but I don't know how to set up Google Workspace SMTP?"

Many people can send and receive emails with Google Workspace without issues, but get stuck when trying to send emails from websites or applications via SMTP.

This article will teach you how to fully configure Google Workspace SMTP, including common WordPress integration.

For complete Google Workspace features, see Google Workspace Complete Guide.

SMTP Basic Concepts

What is SMTP?

SMTP (Simple Mail Transfer Protocol) is the standard protocol for sending emails.

Uses:

  • Website system notifications (order confirmations, password resets)
  • Application reminders
  • Notifications from printers, scanners, and other devices

Why configure SMTP?

Websites or applications need a "mail server" to send emails. You can:

  • Set up your own mail server (very complex)
  • Use third-party services (SendGrid, Mailgun)
  • Use Google Workspace SMTP (focus of this article)

Google Workspace SMTP Options

Google Workspace offers three SMTP sending methods:

MethodAuthenticationLimitSuitable For
Gmail SMTPAccount password/OAuth2,000/day (paid accounts; 500/day on trials)Small volume
SMTP RelayIP whitelist10,000/dayInternal systems
External SMTPAccount passwordVariesThird-party integration

Gmail SMTP Setup

This is the most common method, suitable for small websites or applications.

Server Configuration Information

ItemValue
SMTP Serversmtp.gmail.com
Port587 (TLS) or 465 (SSL)
Authentication RequiredYes
AccountYour Google Workspace Email
PasswordApp password (not regular password)

Step 1: Generate App Password

Google doesn't allow direct SMTP login with account password; you need to generate an "App Password."

Prerequisite: Account must have Two-Step Verification (2FA) enabled

Generation steps:

  1. Go to Google Account Security
  2. Find "2-Step Verification"
  3. Click "App passwords"
  4. Select "Other," enter a name (e.g., "WordPress")
  5. Click "Generate"
  6. Note down the 16-character password generated

Note: This password is only shown once; save it securely.

Step 2: Test Connection

After configuration, test if emails can be sent normally.

Test with Telnet (advanced):

telnet smtp.gmail.com 587

Test with online tools: Search "SMTP Test Tool" and enter your configuration to test.


Having Trouble with Setup?

SMTP setup involves multiple components; one mistake and emails won't send. Let us help quickly resolve setup issues.


SMTP Relay Setup (Enterprise Use)

If you have multiple systems sending emails or high sending volume, SMTP Relay is recommended.

SMTP Relay vs Gmail SMTP

ItemGmail SMTPSMTP Relay
AuthenticationAccount passwordIP whitelist
Daily limit2,000 emails (paid accounts; 500 on trials)10,000 emails
Configuration locationPer userAdmin Console
Suitable forSmall applicationsEnterprise internal systems

Configuration Steps

Step 1: Enter Admin Console

  1. Log into admin.google.com
  2. Go to "Apps" → "Google Workspace" → "Gmail"
  3. Click "Routing"

Step 2: Configure SMTP Relay

  1. Click "Configure" under "SMTP Relay service"
  2. Set allowed senders:
    • Only registered apps in my domains
    • Or only users in my domains
  3. Set authentication method:
    • Only accept mail from specified IP addresses
    • Enter your server IP
  4. Set encryption:
    • Recommend "Require TLS encryption"

Step 3: Note Configuration Information

ItemValue
SMTP Serversmtp-relay.gmail.com
Port587 (TLS) or 465 (SSL)
Authentication RequiredNo (if IP whitelist is configured)

Use Cases

  • Internal ERP system notifications
  • Server monitoring alerts
  • Printer scan-to-email
  • Internal applications

WordPress Integration Tutorial

WordPress is one of the most common scenarios requiring SMTP configuration.

Why Configure It?

WordPress defaults to using PHP mail() for sending, but:

  • Many hosts disable this function
  • Sent emails easily go to spam
  • Can't track if successful

After SMTP configuration, emails are sent through Google, greatly improving delivery rates.

Using Plugin Configuration

Recommended plugin: WP Mail SMTP

Installation steps:

  1. WordPress admin → "Plugins" → "Add New"
  2. Search "WP Mail SMTP"
  3. Install and activate

Configuration steps:

  1. Go to "WP Mail SMTP" → "Settings"
  2. Select mailer: "Other SMTP"
  3. Fill in configuration:
FieldValue
SMTP Hostsmtp.gmail.com
EncryptionTLS
SMTP Port587
AuthenticationOn
SMTP UsernameYour Email
SMTP PasswordApp password
  1. Save settings
  2. Send test email

Common Issues

Issue: Not receiving test email

Check:

  • Is app password correct
  • Is 2FA enabled on account
  • Is it in spam folder

Issue: "Cannot connect to SMTP server"

Check:

  • Does host block port 587
  • Try using port 465 (SSL)
  • Confirm SMTP settings are correct

Issue: Email sent but recipient didn't receive

Check:

  • Is it in spam folder
  • Is DNS SPF record correct
  • Does sending address match domain

Want to Use Third-Party Email Service?

If sending volume is high or you need better tracking, you may need a professional email service. Schedule architecture consultation and let us help plan the best solution.


Sending Limits Explained

Google Workspace Sending Limits

Google does not tier Gmail's daily sending limits by Workspace edition — Business Starter, Standard, Plus, and Enterprise all get the same numbers:

ItemLimit
Gmail messages per day (paid Google Workspace account)2,000/day (1,500 for mail merge)
Gmail messages per day (trial account)500/day
Recipients per message2,000 (500 external)
Total recipients per day10,000 (3,000 external)
SMTP Relay10,000 messages per user per rolling 24 hours; max 100 recipients per SMTP transaction

Sources: Gmail sending limits in Google Workspace and Route outgoing SMTP relay messages through Google (checked 2026-08-30).

Note:

  • These are per-user limits
  • The widely-quoted "500/day" is the trial account limit, not the rule for paid accounts
  • The 10,000 SMTP Relay figure is also edition-independent — Enterprise is not "per contract"
  • Exceeding limits results in a temporary block

How to Avoid Hitting Limits?

  1. Distribute sending accounts: Don't use same account for everything
  2. Control sending frequency: Don't send large volumes in short time
  3. Use SMTP Relay: More relaxed limits
  4. Consider professional email services: SendGrid, Mailgun

What If Sending Volume Is High?

If your sending needs exceed Google limits:

Option 1: Multi-account distribution

  • 2,000 per account
  • 5 accounts = 10,000

Option 2: Use professional email services

  • SendGrid: no longer has a free plan (Twilio announced this on 2025-05-27; all free accounts stopped sending 60 days later). What's left is a 60-day trial at 100/day, then $19.95/month minimum
  • Mailgun: free tier is 100/day (not 5,000/month); the entry paid Basic plan is $15/month for 10,000 emails/month
  • Amazon SES: pay-per-volume and very cheap (check AWS's official SES pricing page for current numbers)

Common Error Troubleshooting

Error: 535 Authentication Failed

Causes:

  • Wrong password
  • Not using app password
  • Account doesn't have 2FA enabled

Solutions:

  1. Confirm account has 2FA enabled
  2. Regenerate app password
  3. Confirm password is correct (watch for spaces)

Error: Connection Timed Out

Causes:

  • Host blocks SMTP ports
  • Firewall blocking

Solutions:

  1. Contact host to confirm ports 587/465 are open
  2. Try different port
  3. Switch to other email service

Error: 550 Mail rejected

Causes:

  • Sending address doesn't exist
  • Flagged as spam
  • DNS configuration issues

Solutions:

  1. Confirm sending address is valid Workspace account
  2. Check if SPF record includes Google
  3. Check if DKIM is configured correctly

Emails Going to Spam

Common causes:

  • SPF/DKIM/DMARC not configured
  • Email content flagged as spam
  • Sending address doesn't match domain

Solutions:

  1. Set SPF record:
    v=spf1 include:_spf.google.com ~all
    
  2. Enable DKIM (configure in Admin Console)
  3. Set DMARC policy

For DNS settings, see Google Workspace MX Record Setup Tutorial.

Security Considerations

Protecting App Passwords

  • Don't write passwords in public code
  • Use environment variables or config files
  • Change passwords regularly

IP Whitelist

When using SMTP Relay:

  • Only allow necessary IPs
  • Regularly review whitelist
  • Remove IPs no longer in use

Monitor Sending Activity

  • Regularly check Admin Console email logs
  • Watch for abnormal sending behavior
  • Set sending volume alerts

FAQ

Can personal Gmail be used?

Yes, configuration is similar. But:

  • Daily limit only 500
  • Not suitable for business use
  • Recommend using Google Workspace

Which port is better?

  • 587 (TLS): Recommended, newer standard
  • 465 (SSL): Backup, if 587 is blocked

Is OAuth authentication more secure?

Yes, OAuth doesn't require storing passwords, more secure. But configuration is more complex; for simple sending needs, app password is sufficient.


Need Help with SMTP Setup?

SMTP setup involves DNS, firewalls, authentication, and more; one mistake and emails won't send.

Schedule a free consultation and let us help you quickly complete setup and ensure emails send properly.


Related Reading


References

Need Professional Cloud Advice?

Whether you're evaluating cloud platforms, optimizing existing architecture, or looking for cost-saving solutions, we can help

Book Free Consultation

Related Articles