Gmail is not a A transactional email is the automated message a WordPress site sends in response to a single user action – a password reset, an order confirmation, a form receipt – addressed to the user who triggered it. Read full reference → service. It is a personal and business email platform that happens to expose SMTP, and WordPress mailer plugins can use that SMTP endpoint to relay site notifications. For sites sending fewer than 50 emails per day, this works. For anything beyond that, a purpose-built relay like SMTP2GO or Brevo is cheaper per message, has higher limits, and provides delivery reporting that Gmail does not.
The reason Gmail dominates WordPress email discussions is proximity: most site owners already have a Google account. That existing credential removes a signup step. Whether it removes enough friction to justify the limitations depends on volume and how much visibility into delivery the site requires.
SMTP settings
| Setting | Value |
|---|---|
| Host | smtp.gmail.com |
| Port | 587 (STARTTLS) or 465 (SSL) |
| Encryption | TLS required |
| Authentication | OAuth2 (recommended) or Less Secure App (LSA) access was Google's name for the third-party authentication path that used a plain account password against Gmail's SMTP, IMAP, and POP endpoints. Google shut it down for consumer accounts on 30 May 2022 and for Workspace accounts on 1 May 2025; OAuth, App Passwords, or a different sending provider replace it. Read full reference → |
| Username | Full Gmail address ([email protected] or [email protected] for Workspace) |
Port 25 is not available. Google blocks outbound port 25 from consumer connections and does not offer it on its SMTP endpoint.
Authentication: OAuth2 vs App Passwords
Google removed Less Secure App Access for Workspace accounts in September 2024 (consumer accounts lost access earlier, in 2022). The two remaining authentication paths for SMTP are:
OAuth2 (recommended): The mailer plugin obtains a token via Google’s OAuth consent flow. The user authorises the plugin once; the plugin refreshes the token automatically. This is Google’s intended integration path. Plugins that support it: WP Mail SMTP, FluentSMTP, Post SMTP. Setup requires creating an OAuth client in Google Cloud Console, which takes 5-10 minutes but only happens once.
App Passwords: Available only when 2-Step Verification is enabled on the Google account. Generates a 16-character password that substitutes for the account password in SMTP authentication. Simpler to configure (paste a string into the plugin settings), but Google can revoke App Passwords without notice, and they bypass MFA by design. For a WordPress site, this is acceptable when OAuth setup is impractical, but OAuth is the more durable choice.
For a detailed setup walkthrough, see How to set up App Passwords in Gmail or Gmail OAuth vs App Passwords.
DNS and email authentication
Free Gmail (@gmail.com): Messages sent through smtp.gmail.com from a @gmail.com address are automatically signed with Google’s DKIM key. The d= domain in the DKIM signature is gmail.com, not a domain the sender controls. SPF passes because Google’s servers are in Gmail’s published SPF record. DMARC alignment works (the From: domain is gmail.com, matching the DKIM d= domain). The sender cannot customise any of this: no custom DKIM, no SPF for their own domain, no DMARC policy control.
Google Workspace (custom domain): Workspace users sending from [email protected] can align DKIM, SPF, and DMARC to their own domain. Setup requires publishing three DNS records:
- SPF: add
include:_spf.google.comto the domain’s TXT record. - DKIM: generate a domain key in Admin Console (Apps > Google Workspace > Gmail > Authenticate email), then publish the provided TXT record at
google._domainkey.yourdomain.com. - DMARC: publish a DMARC policy at
_dmarc.yourdomain.com(e.g.v=DMARC1; p=none; rua=mailto:[email protected]).
Once configured, messages sent via smtp.gmail.com from a Workspace account pass SPF, DKIM, and DMARC alignment against the custom domain. This is the minimum authentication standard for any WordPress site sending from its own domain.
Sending limits
Gmail enforces daily sending limits that vary by account type:
| Account type | Daily sending limit | Notes |
|---|---|---|
| Free Gmail (@gmail.com) | 500 messages/day | Rolling 24-hour window |
| Google Workspace (all plans) | 2,000 messages/day | Per-user; rolling 24-hour window |
Google enforces both message-count and recipient-count limits (Workspace: 10,000 recipients/day, 3,000 external). For WordPress, which typically sends one message per recipient, the effective cap is 2,000 sends per day on Workspace and 500 on free Gmail. SMTP connections are additionally limited to 100 recipients per message, though WordPress rarely exceeds one.
Exceeding the daily limit results in a temporary block (up to 24 hours) with the error 421 4.7.0 Temporary System Problem. The account retains access to incoming mail during the suspension.
The SMTP sending limit is the same across all Workspace tiers. Paying for a higher Workspace plan buys storage and admin features, not higher email throughput. A site that needs more than 2,000 emails per day cannot solve this with Google Workspace alone.
For context: SMTP2GO’s free tier allows 1,000 emails per month (200/day), and its $10/month Starter plan covers 10,000/month. Gmail’s 500/day free limit is generous for a personal email account but mediocre for a transactional relay where WooCommerce order confirmations, password resets, and comment notifications each consume quota shared with the owner’s personal correspondence.
Pricing
Gmail itself is free. The sending limits above apply to free accounts.
Google Workspace adds custom domain support, higher limits (2,000/day), admin controls, and proper DKIM alignment. Current pricing (per user, billed annually):
| Plan | Monthly cost | Storage | SMTP limit |
|---|---|---|---|
| Business Starter | $7.20/user | 30 GB/user | 2,000/day |
| Business Standard | $14.40/user | 2 TB/user | 2,000/day |
| Business Plus | $21.60/user | 5 TB/user | 2,000/day |
| Enterprise | Custom | Unlimited | 2,000/day |
Note that the SMTP limit does not increase with plan tier. A site that needs more throughput needs a dedicated sending service, not a higher Workspace plan.
For comparison: Brevo’s free tier sends 300 emails/day with no per-user fee and no storage bundled. SMTP2GO’s $10/month plan sends 10,000/month. Google Workspace at $7.20/user/month is not priced as an email relay; it is priced as a productivity suite that includes email relay as a side feature.
WordPress integration
Gmail works with any WordPress mailer plugin that supports SMTP or Google OAuth2:
| Plugin | OAuth2 support | Notes |
|---|---|---|
| WP Mail SMTP | Yes (built-in wizard) | Most streamlined setup for Gmail OAuth |
| FluentSMTP | Yes | Free; includes Google OAuth flow |
| Post SMTP | Yes | Includes email logging |
| Easy WP SMTP | No (SMTP only) | App Password required |
Plugins with OAuth2 support handle token refresh automatically. Plugins that only support plain SMTP require an App Password.
For setup instructions: Configure Gmail as a WordPress email server.
Limitations
Features standard in purpose-built transactional services that Gmail lacks entirely:
- Delivery webhooks: no programmatic notification when email bounces, is opened, or links are clicked.
- Sending logs with delivery status: Gmail shows "sent" in the Sent folder. It does not report whether the message reached the inbox, was deferred, or bounced. Workspace admin logs exist but are delayed by hours and not designed for per-message monitoring.
- Dedicated IP: all Gmail users share Google’s IP pools. Reputation is pooled; a site cannot build or protect its own sender reputation.
- Bounce handling: bounces return to the sending address. No webhook, no suppression list, no automatic unsubscribe handling.
- Volume burst capacity: the daily cap is hard. A WooCommerce flash sale that generates 600 order confirmations in an hour will hit the free-tier wall.
- Custom DKIM on free accounts: messages from @gmail.com are signed by Google on
gmail.com. The sender’s own domain never appears in the DKIM signature without Workspace.
Verdict
Gmail is appropriate when the site sends fewer than 50 transactional emails per day, the owner already has a Google account, and delivery visibility is not a requirement. Contact form notifications, password resets, WooCommerce order confirmations on a low-volume store: these work over Gmail SMTP without issue.
Gmail is not appropriate when the site needs delivery reporting, sends marketing email, processes high-volume WooCommerce orders, or requires a dedicated sending reputation. At that point the correct answer is a transactional relay: SMTP2GO for simplicity, Postmark for deliverability focus, or Brevo if the site also needs marketing campaigns.
The most common failure mode with Gmail as a WordPress SMTP relay is not technical but operational: the site outgrows the daily limit, emails start silently failing (WordPress does not surface SMTP quota errors to the admin by default), and the owner discovers the problem only when a customer reports a missing order confirmation. A logging plugin like Check & Log Email mitigates this, but does not solve the underlying capacity constraint.
For the broader setup that places Gmail inside the WordPress email stack, see the WordPress email setup guide.