Adds a simple, no-fuss SMTP settings to your WordPress installation that lets you define custom settings, which is especially useful for hosts with no control over the php
If logging is enabled, a new segment in the settings panel will show up with a 30-day overview of recent emails, and will automatically prune older logs. Please see the FAQ if you want a more permanent solution.
For more information, please see the project wiki on GitHub.
Environment and constant overriding (optional)
This plugin will prefer environmental and constant-stored values over the plugin-saved equivalent settings, making it easier to use this plugin via deployment.
These can be either stored in your systems env setup, or in wp-config.php as
define( 'SEE_BELOW', 'your_value_here' );.
SMTP_HOST(string) Mail server hostname.
SMTP_PORT(integer) Port address (usually 25, 465 or 587).
SMTP_AUTH(integer, 1 or 0) Pass below credentials to your mail server.
SMTP_USER(string) The mail username for this account.
SMTP_PASS(string) The password for the mailer account.
SMTP_FROM(string) Enforce all emails come from this email address.
SMTP_FROMNAME(string) Enforce all emails to have a certain email name.
SMTP_SEC(string) Use a particular email security method (accepts ‘def’ (default), ‘ssl’ and ‘tls’).
SMTP_NOVERIFYSSL(boolean) Disable validation of the SMTP server certificate (not recommended).
SMTP_LOG(boolean) Controls the logging capability and visibility.
SMTP_DISABLE(boolean) Disables the mailer. They will still be logged if enabled, but won’t send out.
It is recommended to store at least
SMTP_PASS in your wp-config.php file (with the correct file permissions set). If the openssl extension is available, the plugin will attempt to encrypt the password in the database.
Часто задаваемые вопросы
How do I fix SMTP errors?
This plugin works by instructing PHPMailer — the mail library WordPress have chosen — to use SMTP mode, and adds in the settings you choose. 9 times out of 10, the error messages you receive are configuration errors. PHPMailer provides a good guide to help you figure out these problems.
The one instance where an SMTP error can be caused by this plugin is if the SMTP password is stored in the database when the secret keys have been regenerated. You will need to re-save the password to refresh the encryption keys.
You can always get assistance from your host and/or SMTP service provider.
When using the logging functionality, the plugin will store the logged emails in the posts table, as an invisible post type. Normally this should work completely fine, but if you have a plugin that scans custom post types and sends an email about them, there’s a chance the third-party plugin might get stuck in a loop. For plugins like this, it is best to disable the functionality on the logging post type (sbss_email_log).
The following plugins have had reported issues:
* Sucuri Security.
One or more of the settings are greyed out
This plugin supports being overridden by DEFINE, so please check to see that you are not setting a define for a WP Simple SMTP option. These are most commonly stored in the wp-config.php file.
The over-ride hierachy is as follows, with top being the most important.
- Environmental variable.
- Constant variable (wp-config define).
- Multisite network settings.
- Locally-configured settings.
How do I stop the logs from automatically purging?
The logs by default will auto-prune to avoid keeping sensitive details in logs and contributing to database bloat. But if you wish to keep the logs more permanently, then register the following hook (typically in your theme functions.php) to disable the auto-pruning functionality:
add_filter( 'simple_smtp_disable_log_prune', '__return_true' );
How is the SMTP password stored?
If openssl is available to PHP, then the password will be encrypted (not hashed) when stored in the database. If unavailable, the SMTP password will be saved into the database as plaintext. The more recommended way of storing the password is to define SMTP_PASS in your wp-config.php file, which should already be locked and inaccessible from the front-end.
Note: Multisite over-ride password is currently not encrypted. Please see this issue.
Can I change the amount of entries shown in the log view?
This can be adjusted by the ‘simple_smtp_log_table_max_per_page’ filter. Returning an integer value to this filter hook will adjust the table page limit.
Does this plugin support WordPress CLI?
Yes. With WP-CLI you can perform the following actions:
email-logView the log if enabled.
email-testSend a test email.
To view the available options and help documentation, run
wp help <function name>.
Does this plugin work on WordPress Multisite?
Yes. Each site can have unique settings, unless overriding is on. The network will use the main site settings, so network admin emails will show up in the main site log.
Since version 1.2, network-activating the plugin grants special configuration options for super administrators. This includes the ability to set overrides and configure site admin access.
Why do I see capital texts next to the input boxes? (Debugging disabled input boxes)
To help diagnose disabled input boxes, when the WordPress site is in debugging mode, the input fields will show a small debug text to indicate where the setting came from.
- CONFIG is the standard method of saving settings via the admin menu.
- CONST are overrides typically set in either wp-config.php or your theme’s functions.php.
- MULTISITE are network-defined overrides set in the Network Mail panel.
- ENV are pulled from the machine/server environmental settings.
Can I report an issue, or contribute to development?
Yes! Please see our GitHub repository here for writing issues and/or making pull requests.
One of the easiest aspects to contribute to is the SMTP quick configuration segment. If you wish to maintain this aspect, suggest a new setting, or report broken entries, see the SMTP quick config wiki page.
Участники и разработчики
«WordPress Simple SMTP» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:Участники
- Verified working with WordPress 6.1 and 6.2.
- Fix: PHP warning on the CLI interface (#140).
- Rollback: #116 fix regressed due to relying on a function not found in the general scope.
- Added: Mail view now displays from, cc, bcc & the headers stored when logging is enabled.
- Fix: Infinite loop when a plugin hooks into the mail routine functions and sends an email (#116).
- Verified working with WordPress 6.0.
- Added: Glance view on the dashboard to see mail usage (Thanks Kebbet — PR 101, PR 102).
- Fix: Table view appears correctly on mobile (Thanks Kebbet — PR 93).
- Fix: Log view table navigation (Thanks Kebbet — PR 106).
- Added: Read logged emails via WP-CLI.
- Added: Status message from testing emails (#81).
- Change: Uninstalling the plugin will remove the lingering logs (#70).
- Change: (For new installs) logs purge automatically after a month (#71).
- Change: Quick config settings now contained within plugin (#78).
- Change: Tightened permissions to the log viewer (#74).
- Fix: Incorrect capability type used by the log viewer. Thanks to Benoît Chantre #74.
- Add: WordPress CLI support. See the FAQ for usage details.
- Change: Password not returned plaintext in settings (#61).
- Fix: Multisite-only config caused an instantiation error (#67).
- Add: Filter for the log entries. Thanks to Kebbet #57.
- Change: Input boxes clearer and more WordPress-standardised (#51, #52).
- Fix: Use network_admin_url instead of crafting a URL. Thanks to Kebbet #53.
- Fix: Notice when saving settings without password being set (#44).
- Change: Multisite listing table improvements. Thanks to Kebbet (#50).
- Fix: Line break issue when viewing emails in the site log. Thanks to Kebbet #47.
- Fix: Missed localisations in the multisite table. Thanks to Kebbet #45.
- New: Multisite settings for admin visibility and override settings (#6).
- New: Sites in debug mode will show what stage has set the configuration item in the relevant box.
- New: For sites using logging, ‘Erase Personal Data’ will remove requested email address entries from the log (#37).
- Verified working with WordPress 5.8.
- Verified working with WordPress 5.7.
- Fix: Crash when sending emails with the email system disabled (#35).
- New: You can now disable emails (#9).
- New: Attachments are now logged, and will be resent if they are still available on the system (#14).
- New: Key change detection when SMTP password encryption is used, to warn user the email dispatch may fail (#28).
- Change: Custom HTML removed in favour of translatable HTML test email. Thanks to Kebbet for implementation (#26).
- Fix: Quick config translations not loading, and missing i18n entities. Thanks Kebbet (#21).
- Fix: Incorrect pagination if the log count was divisible by 5. Thanks Kebbet (#18).
- Fix: Text-domain mismatch causing translations not to load in correctly. Thank you to Kebbet for the fix (#19).
- When openssl is available, the password stored in the database will be encrypted.
- Added a quick configuration option, to guide SMTP setup (less Googling).
- Confirmed working with WordPress 5.5.1.
- Added option to disable SSL verification.
- Multiple emails can be used in the test functionality.
- Independent log tables deprecated for CPT.
- Changed display format of email log.
- Limit resent emails to hourly.
- Table is created or deleted upon plugin state change.
- Changes to test emails.
- Log view changed depending on header.
- SMTP error logging.
- View and resend emails.
- Test email settings.
- SMTP configuration handling (overrides
- Optional SMTP logging (basic functionality).