Log emails to the database, to enable email problem analysis
Log emails to the WordPress database for later analysis. Access is restricted to administrators, and emails with WordPress passwords are obfuscated for security / privacy. Useful for diagnosing lost email problems.
Use this plugin with Disable Emails to divert all WordPress emails into logs, especially handy for developers.
Logs are automatically purged after a defined period, set through a settings page in the WordPress admin. Setting the period to 0 prevents logs from being purged. Uninstalling the plugin purges all logs.
Many thanks to the generous efforts of our translators:
If you’d like to help out by translating this plugin, please sign up for an account and dig in.
You probably have a plugin that is sending emails via some other method, like directly using the PHP mail()
function, or directly implementing an SMTP client. Not much I can do about that…
Some plugins tell WordPress that their emails are HTML, using one of two accepted methods. These emails are correctly recorded as HTML and should display reasonably well in the logs. If they use CSS, they might not display exactly like they do in an email program, but should still display OK.
Some plugins just dump HTML into emails without saying it’s HTML, or even following basic HTML document rules. If those emails have an alternative body, implying HTML + plain text parts, they’ll be marked as HTML and will display as such.
If you find that emails from some plugins are broken, please tell me in the support forum.
Logging emails writes to the database. The plugin uses a custom post type, so logging each email has the same impact as saving a new WordPress post, i.e. generally not much.
The full changelog can be found on GitHub. Recent entries:
Released 2020-10-13
$typenow
breaks some other plugins (e.g. Event Espresso)