Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

Smmooth WP Plugins

Bryan Ho

Smooth SMTP gives you full control over how WordPress sends email. Configure SMTP as your primary sending method, set up a fallback for when things go wrong, get notified through your preferred channels, and keep a detailed log of every email your site sends.
Primary Sending Method (SMTP)
Configure any SMTP provider as your primary sending method. If you leave SMTP disabled, WordPress will continue using its default PHP mail — either way, all other features still work.
<ul>
<li>Works with any SMTP provider: Gmail, SendGrid, Amazon SES, Mailgun, and more</li>
<li>Configurable host, port, encryption (SSL/TLS), username, password, from email, and from name</li>
<li>Secure credential storage using WordPress’s built-in options API</li>
</ul>
Fallback Sending Method
If the primary sending method fails, Smooth SMTP can automatically retry using a fallback. This works regardless of whether you’re using SMTP or WordPress’s default PHP mail as your primary.
<ul>
<li>Fallback to WordPress Default (PHP mail) or a second SMTP server</li>
<li>Full credential configuration for the fallback SMTP</li>
<li>Logged separately so you can see exactly which method delivered each email</li>
</ul>
Failure Alert Channels
Get notified the moment an email fails — through the channels your team already uses.
<ul>
<li>Slack, Discord</li>
<li>Telegram (via Bot API — requires bot token and chat ID)</li>
<li>WhatsApp (via CallMeBot webhook)</li>
<li>SMS or any custom webhook endpoint</li>
<li>Add multiple channels, enable/disable each independently</li>
<li>Send Test Alert button per channel</li>
<li>Alerts are throttled to at most one per 60 seconds to avoid flooding</li>
</ul>
Email Summary Reports
Receive a periodic HTML email summarising your site’s email activity.
<ul>
<li>Hourly, daily, weekly, or monthly schedule</li>
<li>Total sent and failed counts, breakdown by sending method, and recent failures</li>
<li>Configurable recipient address</li>
<li>Send Summary Now button for an instant preview</li>
</ul>
Email Logging
Every email your site sends is logged with full detail.
<ul>
<li>Status (success / failed), sender, recipients, subject, message body</li>
<li>Sent Via column showing which method delivered the email (Primary SMTP, Fallback SMTP, Fallback WordPress Default, etc.)</li>
<li>Search, filter, and paginate logs from the admin dashboard</li>
<li>View full email detail in a modal</li>
<li>Bulk delete, bulk resend, and delete-all options</li>
<li>Admin dashboard notice when the most recent email failed</li>
</ul>
Dashboard
A at-a-glance overview of your site’s email activity.
<ul>
<li>Total sent, failed, and success rate stat cards</li>
<li>Breakdown by sending method with progress bars</li>
<li>Recent failures table</li>
<li>Filter by day, week, month, or all time</li>
</ul>
Test Email
Send a test email at any time to verify your configuration.
<ul>
<li>Choose which sending method to test — primary or fallback — independently</li>
<li>Send plain text or HTML test emails</li>
<li>Specify any recipient address</li>
<li>Always available regardless of whether SMTP is configured</li>
</ul>
Other
<ul>
<li>One-click import of email logs from Post SMTP</li>
<li>Option to keep logs and settings when the plugin is deleted</li>
<li>Compatible with Post SMTP and WP Mail SMTP (Smooth SMTP acts as a fallback when another SMTP plugin is detected)</li>
</ul>
<h3>Privacy Policy</h3>
This plugin logs email metadata including sender address, recipient addresses, subject line, message body, and sending status. SMTP credentials are stored in your WordPress database. No data is transmitted to external services except through the alert channels and SMTP servers you explicitly configure.

Smooth SMTP

SMTP configuration, email logging, failure alerts, and fallback sending for WordPress.

Observer vs Smooth SMTP