WordPress Simple SMTP

Description

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 mail functionality.

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' );.

Accepted Parameters

  • 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.

FAQ

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.

Troubleshooting – PHPMailer.

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.

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.

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.

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. More multisite related functionality will be added.

Can I report an issue, or contribute to development?

Yes! Please see our GitHub repository here for writing issues and/or making pull requests.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“WordPress Simple SMTP” is open source software. The following people have contributed to this plugin.

Contributors

“WordPress Simple SMTP” has been translated into 1 locale. Thank you to the translators for their contributions.

Translate “WordPress Simple SMTP” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.1.1

  • Verified working with WordPress 5.7.
  • Fix: Crash when sending emails with the email system disabled (#35).

1.1.0

  • 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: JavaScript error when viewing emails (#24).

1.0.2

  • 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).

1.0.1

  • Fix: Text-domain mismatch causing translations not to load in correctly. Thank you to Kebbet for the fix (#19).

1.0.0

0.3.6

  • SMTPSecure is now a configurable option (#11).
  • Log entries can now be deleted (#13).

0.3.5

  • When openssl is available, the password stored in the database will be encrypted.
  • Added a quick configuration option, to guide SMTP setup (less Googling).

0.3.4

  • Confirmed working with WordPress 5.5.1.
  • Added option to disable SSL verification.
  • Multiple emails can be used in the test functionality.

0.3.3

  • Independent log tables deprecated for CPT.

0.3.2

  • Changed display format of email log.
  • Limit resent emails to hourly.

0.3.1

  • Table is created or deleted upon plugin state change.

0.3

  • Changes to test emails.
  • Log view changed depending on header.

0.2

  • SMTP error logging.
  • View and resend emails.
  • Test email settings.

0.1

  • SMTP configuration handling (overrides mail()).
  • Optional SMTP logging (basic functionality).