Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallYou can route WordPress emails through a Gmail or Google Workspace account by configuring a mailer plugin. The most straightforward documented option is a plugin’s Google/Gmail mailer, which uses Google’s API and OAuth authorization; generic SMTP is a separate route that uses Google’s SMTP server settings. These setup paths are not interchangeable.
Choose how WordPress will connect to Google
WordPress and its plugins generate messages such as password resets, form notifications, and order updates. A mailer plugin can route those messages through a Google account instead of relying on the web host’s default mail handling. The plugin manages the connection; this does not change where messages originate in WordPress.
| Route | What it uses | Considerations |
|---|---|---|
| Google/Gmail mailer in a plugin | Google API and OAuth authorization, as documented for WP Mail SMTP | Guided account authorization; requires the plugin’s Google configuration. See WP Mail SMTP’s Gmail and Google Workspace setup guide. |
| Plugin one-click setup | A vendor-guided Google connection option | Check whether the option is available in your plugin and plan. See WP Mail SMTP’s one-click setup instructions. |
| Generic Gmail SMTP | Google’s SMTP server, with TLS or SSL and an authentication method supported by the account and plugin | Requires outbound SMTP access from the host and correct authentication. Google lists the endpoint and ports in its Gmail IMAP, POP, and SMTP documentation. |
If your plugin offers a Google/Gmail API mailer, its OAuth flow avoids treating an ordinary account password as an SMTP credential. Use generic SMTP only when that is the route you intend to configure and your account, plugin, and host support it.
Set up the Google/Gmail API mailer
The exact labels and availability vary by plugin. The following sequence reflects the Google/Gmail setup documented by WP Mail SMTP; use the current guide for the controls shown in your own dashboard.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- In WordPress, install and activate your chosen mailer plugin. Open its mailer settings and select Google or Gmail for the API-based route.
- Choose the available connection method. If the plugin offers one-click setup and it suits your account, follow its current prompts. Otherwise, follow the plugin’s Google project and OAuth instructions.
- For the manual OAuth route, configure the Google project as the plugin specifies: enable the Gmail API, complete the consent or application details, create the correct OAuth client, and enter the redirect URI supplied by the plugin. Save the client credentials where the plugin requests them. Google Console labels may change, so follow the live plugin and Google instructions rather than relying on an old screen name.
- Authorize the Google account that should send the site’s email. Review the plugin’s From Email and sender-name settings, and use the account or an authorized sender identity appropriate to that account.
- Save the settings and send a test email using the plugin’s test function. A successful test means the test message was submitted through the configured route; it does not establish that every future message will arrive in an inbox.
For one-click setup, follow the vendor’s current instructions at WP Mail SMTP’s one-click setup guide. Do not mix its OAuth/API screens with the host, port, and encryption fields used for generic SMTP.
Configure generic Gmail SMTP
If your plugin requires manual SMTP settings, Google documents smtp.gmail.com as the server. Use the port and encryption pairing below, then configure authentication according to the current requirements of your Google account and plugin.
| SMTP setting | Value |
|---|---|
| SMTP host | smtp.gmail.com |
| Port with TLS | 587 |
| Port with SSL | 465 |
| Authentication | Use an authentication method supported by Google, your account, and the plugin; OAuth 2.0 is supported for Gmail SMTP. |
Google’s protocol documentation covers the server and ports, while its Google Workspace third-party email client guidance recommends OAuth-capable clients and describes app passwords for situations where OAuth cannot be used. An app password is only a conditional fallback subject to Google’s account requirements; it is not available for every account. Do not enter your ordinary Google account password into a plugin as a generic SMTP password.
Check sending limits and delivery expectations
SMTP changes the route WordPress uses to submit mail; it does not guarantee delivery or inbox placement. Google warns that suspicious messages may be filtered. Check spam or junk folders and assess whether the account’s policies and sending limits fit the site’s needs, especially for high-volume or operationally critical transactional email.
Recommended Free Tools
Google Workspace’s guidance for sending from an app lists a limit of 2,000 messages per day for its documented Gmail SMTP option. That figure is specific to the Workspace route described on Google’s page; it should not be applied to personal Gmail accounts, the Gmail API, or every Workspace plan. Check Google’s current, account-specific guidance before relying on a limit. See Google Workspace: Send email from a printer, scanner, or app.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot Gmail mailer problems
Google authorization fails
Confirm that you followed the selected plugin’s current OAuth setup, especially the redirect URI, OAuth client type, and account authorization. If Google shows a consent or application-status error, follow the instructions on the current Google and plugin screens; menu labels can change.
Google rejects the credentials
Check that the selected mailer matches the credentials you configured and that you authorized the intended account. Google documents SMTP errors for rejected credentials and cases where an application-specific password is required. See Gmail SMTP errors and codes. Do not try to fix a rejected login by entering the account’s ordinary password into an unsupported client.
The connection times out
A timeout points to the network path between your WordPress host and Google, rather than necessarily to an OAuth problem. Confirm that the host permits outbound SMTP on the port you selected, and check the host’s current network policy. Google’s documented SMTP ports are 587 for TLS and 465 for SSL.
The test sends but recipients cannot find the message
Check the recipient address and spam or junk folders. If your plugin provides logs, review them; also check for account restrictions or a sending limit. A successful test confirms submission through the configured route, not inbox placement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
