Gmail SMTP plugin allows you to authenticate with your Gmail account to send email via Gmail SMTP server.
Most shared hosting servers have restrictions when it comes to email. Usually email will get blocked or missing for no reason. Sometimes it will get blocked when your website reaches the daily limit of outgoing email. This plugin can bypass this issue by routing the email through Gmail’s SMTP server.
Gmail SMTP Add-ons
Gmail SMTP Benefits
- Gmail SMTP plugin is not like most SMTP plugins. It uses the OAuth 2.0 protocol to authorize access to the Gmail API – which means a more secure login system and users won’t have to enter any username or password.
- Gmail SMTP plugin uses PHPMailer – a very popular library used for sending email through PHP’s mail function. This libary is also used in the core WordPress to send email.
- Gmail SMTP plugin utilizes “wp_mail” (A function used by WordPress to send email) instead of completely overriding it. This way you still get all the benefits of the default mail function.
- You no longer need to enable Allow less secure apps on your gmail account to fix SMTP connection issue. This issue became prominent from December 2014, when Google started imposing XOAUTH2 authentication (based on OAuth2) to access their apps. This issue still affects almost all the SMTP plugins because they authenticate via username and password.
How OAuth 2.0 Authorization Works
- You register an application in the Google Developers Console.
- The application is launched and it requests that you give it access to data in your Google account.
- If you consent, the application receives credentials to access the Gmail API.
Gmail SMTP Features
- Configure your website to send email using Gmail SMTP server
- Authenticate using OAuth 2.0 protocol
- Authenticate with encryption when sending an email (TLS/SSL)
Gmail SMTP Basic Setup
- Create a new project in Google Developers Console.
- Enable Gmail API in it.
- Create credentials (OAuth client ID) to access this API.
- Configure the consent screen for the web application.
- Once the consent screen is configured, create a web application.
- Go to the plugin settings (
- Set the Authorized Redirect URL of the application as the one shown in the settings.
- Finish creating the web app.
- Copy the newly created Client ID and Client secret and paste into the settings area.
- Enter your OAuth Email, From Email and From name.
- Select an encryption.
- Enter a port number.
- Save the settings.
- Now you can authorize your application to access the Gmail API by clicking on the Grant Permission button.
- Once the application has been authorized Gmail SMTP plugin will be able to take control of all outgoing email.
Gmail SMTP Settings
- Authorized Redirect URI: Authorized redirect URL for your website. You need to copy this URL into your web application.
- Client ID: The client ID of your web application.
- Client secret: The client secret of your web application.
- OAuth Email Address: The email address that you will use for SMTP authentication. This should be the same email used in the Google Developers Console.
- From Email Address: The email address which will be used as the From Address when sending an email.
- From Name: The name which will be used as the From Name when sending an email.
- Type of Encryption: The encryption which will be used when sending an email (TLS/SSL. TLS is recommended).
- SMTP Port: The port which will be used when sending an email. If you choose TLS it should be set to 587. For SSL use port 465 instead.
- Disable SSL Certificate Verification: As of PHP 5.6 a warning/error will be displayed if the SSL certificate on the server is not properly configured. You can check this option to disable that default behaviour.
Gmail SMTP Test Email
Once you have configured the settings you can send a test email to check the functionality of the plugin.
- To: Email address of the recipient.
- Subject: Subject of the email.
- Message: Email body.
For detailed setup instructions please visit the Gmail SMTP plugin page.
- Go to the Add New plugins screen in your WordPress Dashboard
- Click the upload tab
- Browse for the plugin file (gmail-smtp.zip) on your computer
- Click “Install Now” and then hit the activate button
Can I send email from my Gmail account using this plugin?
Can this plugin use OAuth 2.0 to send email?
Can I use this plugin for Gmail signup?
Can I use this plugin on Gmail app?
Can I use this plugin to access my Gmail inbox?
Can I use this plugin to sign out of my Gmail account?
བྱས་རྗེས་འཇོག་མཁན། & གསར་འབྱེད་པ།
“Gmail SMTP” is open source software. The following people have contributed to this plugin.བྱས་རྗེས་འཇོག་མཁན།
“Gmail SMTP” has been translated into 8 locales. Thank you to the translators for their contributions.
ཁྱེད་ཀྱི་སྐད་ཡིག་ནང་ལ་ “Gmail SMTP” ཡིག་སྒྱུར་བྱོས།
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
- Added support for the Cc add-on.
- Added support for the Reply-To add-on.
- Compatibility update for WordPress 6.1.
- Updated the mail function for WordPress 6.0.
- Fixed an issue that could cause an Undefined variable error if $attachments was not set.
- Updated the mail function for WordPress 5.9.
- Updated for WordPress 5.8.
- Updated the help text for the From Email Address field.
- WordPress 5.7 compatibility update.
- WordPress 5.5 compatibility update.
- Gmail SMTP is compatible with WordPress 5.3.
- Fixed this warning that is shown on servers running on PHP 7.2 or higher: PHP Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in /wp-content/plugins/gmail-smtp/PHPMailer/PHPMailerAutoload.php on line 45
- Added some error handling code after the authorized redirection step. This is to make sure that the plugin doesn’t save the error if an error occurs and no access token is returned.
- Updated the PHPMailer library to version 5.2.26. This release fixes a potential XSS vulnerability in the default debug output.
- Gmail SMTP is now compatible with WordPress 4.9.
- Updated the minimum requirements for PHP to 5.6 since it was causing a curl_reset() error in the Google API Client library.
- Made some changes to only include the Google API Client library and PHPMailer when needed.
- Updated the Google API Client library to version 2.2.0.
- Updated the PHPMailer library to version 5.2.24. This release contains a security fix for XSS vulnerability CVE-2017-11503.
- Removed the “Basic Setup Instructions” section from the settings page. Full setup instructions are now available on the documentation page.
- Updated the PHPMailer library to version 5.2.22. This release contains a critical security fix for CVE-2017-5223.
- Updated the PHPMailer library to version 5.2.21. This release contains a critical security update for CVE-2016-10045 that was fixed in PHPMailer 5.2.20.
- Updated the PHPMailer library to the latest version (5.2.19). This release also contains a critical security update for CVE-2016-10033 that was fixed in PHPMailer 5.2.18.
- Gmail SMTP now supports the “wp_mail_failed” hook which fires after a phpmailerException is caught.
- Added more requirements to the Server Info tab to help with troubleshooting.
- Compatible with WooCommerce email in HTML format.
- Added a new option to bypass this error on some servers where the SSL certificate is not properly configured – Warning: stream_socket_enable_crypto(): SSL operation failed with code 1.
OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
- Fixed a bug that was causing this error – “Strict Standards: Non-static method GmailXOAuth2::getClient()”
- google-api-php-client’s autoloader path now points to the src directory as the current autoloader has been deprecated
- Gmail SMTP plugin is now compatible with WordPress 4.4
- Added a new tab to show some server related information
- More debug data will be shown when sending a test email
- Fixed a bug where the oauth URL was pointing to localhost
- First commit