Stefano Lissa

<p>When it’s important to record what happens in your site internal, this plugin is an handy tool.</p>
<p>It can track abilities calls, http calls, record the result and in particular the filters attached to them that can modify the bahavior.</p>
<p>It’s perfect to be used side-by-side with other logging and monitoring plugins, like wp mail logging and query monitor.</p>
<p>It can collect a lot of data, but you can change the retention period on your needs.</p>
<p>When unistalled all the logged data and settings are cleaned up.</p>
<p>Please, <a href="//www.satollo.net/plugins/monitor" rel="nofollow ugc">read the official page for more details</a>.</p>
<h4>What’s monitored</h4>
<ul>
<li>Emails</li>
<li>HTTP calls (using the wp_remote_* functions)</li>
<li>REST API calls</li>
<li>Scheduler runs with detailed jobs data</li>
<li>Abilities invocation</li>
<li>AI Client calls (WP 7.0+)</li>
</ul>
<p>Please, <a href="https://www.satollo.net/plugins/monitor" rel="nofollow ugc">read the official page for more details</a> for more detail, examples of problems and solutions.</p>
<h4>Contacts, Requests, Bugs</h4>
<p>Please, contact me using the support forum or directly if you find problems or have new monitoring ideas.</p>
<h4>Tech details</h4>
<ul>
<li>All logged data is stored on your WP database (nothing is sent externally!) into dedicated tables named wp_monitor*.</li>
<li>The HTTP tests (ok, bad, not found) just calls my site (https://www.satollo.net) to produce a log, nothing is stored on my side</li>
<li>The email tests, send an email to the admin address configured on your site (see the WP Settings)</li>
</ul>


Monitor: Scheduler, Emails, API, HTTP and more

Track and store internal WP events for analysis and debugging: abilities calls, http calls, emails, scheduled jobs, ...

JWardee

<p>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.</p>
<p>Just install and activate then all of your contact form emails will be logged and saved to your DB with no additional configuration required.</p>
<p>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.</p>
<p>Send emails out directly from the WordPress interface. Also includes support for attachments.</p>
<p>Immediately find out if your contact form submission was successfully sent.</p>
<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

Monitor: Scheduler, Emails, API, HTTP and more vs Mail logging – WP Mail Catcher