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.

JWardee

Logging your mail will stop you from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages.
Just install and activate then all of your contact form emails will be logged and saved to your DB with no additional configuration required.
View and manage all your form submissions through the default WordPress interface. An email failed to send? With a single click you can resend the backed up email.
Send emails out directly from the WordPress interface. Also includes support for attachments.
Immediately find out if your contact form submission was successfully sent.
<h3>Features</h3>
<ul>
<li>Zero setup required – just install and away you go</li>
<li>Minimalistic – no overbloated features you never use weighing your site down – under 140kb in size!</li>
<li>Bulk export emails to CSV for easy inclusion into Excel or any other program</li>
<li>Compose new emails with the WordPress controls you’re already familiar with</li>
<li>Resend your emails in bulk</li>
<li>Debugging – see exactly which file and code line was responsible for sending the email, along with any errors encountered</li>
<li>Manage what user permissions can see the logs</li>
<li>Routinely have your logs cleared out at a specified time – or keep them forever</li>
<li>Need to be notified when there’s a problem sending your mail? We’ve got hooks that allow you to do just that</li>
<li>Completely free</li>
</ul>
<h3>Hooks and actions</h3>
<ul>
<li><code>wp_mail_catcher_mail_success</code> is triggered when a message is sent and logged successfully. It has a single argument that is an array containing the log
<ul>
<li><code>id</code> related to the id in the <code>mail_catcher_logs</code> MySQL table</li>
<li><code>time</code> relative, readable time to when the log was saved</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>status</code> an integer depicting if the message was sent successfully or not (1 = sent successfully. 0 = sending failed)</li>
<li><code>error</code> the error that occurred – if any</li>
<li><code>backtrace_segment</code> a json_encoded object that shows which file and line the mail was initially triggered from</li>
<li><code>attachments</code> a list of any attachments that were sent along with the email</li>
<li><code>additional_headers</code> a list of any headers that were sent</li>
<li><code>attachment_file_paths</code> a list of the location of any attachments that were sent</li>
<li><code>timestamp</code> a unix timestamp of when the email was sent</li>
<li><code>is_html</code> a boolean, that will be true if the message is a html email and false if not</li>
<li><code>email_from</code> the from value of the email</li>
</ul>
</li>
<li><code>wp_mail_catcher_mail_failed</code> is triggered when a message failed to send and logged successfully. It has a single argument that is an array containing the log (same as the arguments for <code>wp_mail_catcher_mail_success</code>)</li>
<li><code>wp_mail_catcher_deletion_intervals</code> is a filter that should return an array where each key is an amount of time in seconds, and the value is the label. Used to determine when a message has expired and should be deleted</li>
<li><code>wp_mail_catcher_before_success_log_save</code> is a filter that is called just before a successful log is saved. It has a single argument that is the transformed log that will be saved – use this to alter the log before it’s saved. Returning <code>false</code> will stop the log from being saved. Also note that this is fired even when an email has errored, because all logs are initially saved as “successful” before being possibly updated with an error (if applicable). This is because of the way the <code>wp_mail</code> and <code>wp_mail_failed</code> are implemented in WordPress.
<ul>
<li><code>time</code> a unix timestamp of when the email was sent</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>backtrace_segment</code> an array that shows which file and line the mail was initially triggered from</li>
</ul>
</li>
<li><code>wp_mail_catcher_before_error_log_save</code>
<ul>
<li><code>time</code> a unix timestamp of when the email was sent</li>
<li><code>email_to</code> the email address(es) that the message was sent to</li>
<li><code>subject</code> the subject line of the message</li>
<li><code>message</code> the contents of the message</li>
<li><code>backtrace_segment</code> an array that shows which file and line the mail was initially triggered from</li>
<li><code>error</code> the error that occurred</li>
</ul>
</li>
</ul>

Mail logging – WP Mail Catcher


Works great. It needs a some adjustments though on mobile screens.


Works Great


Really well done thank you!Very useful debug function with the code that sent the email!


Keeps track of all emails sent


Works perfectly as expected, every single time, for years and years!


The Best!

just perfect!


simple and lightweight. with this you have the absolute control over what was successfully send. besides that you can also send a manual email from the dashboard. nice


Perfect companion for wp mail smtp or wpo365


This is a great extension, and does everything that you need of an email logging extension. 



Very useful for debugging purposes!


Easy to use, with no bloat.


tested it for a few weeks and it's very fine, lite and fast.



only one small proposal: option to redirect an email - some users input their email wrong and admins can see this and redirect to the correct email address (ex. @yhoo.com instead of yahoo.com)


perfect for mail logging and preview

Stop from ever losing your emails again! This fast, lightweight plugin (under 140kb in size!) is also useful for debugging or backing up your messages

Observer vs Mail logging – WP Mail Catcher