Patrick

Hi @adriel05,

Thanks for taking the time to leave a review and for the honest feedback, glad to hear WP Mail SMTP got your emails flowing again!

You mentioned the setup took a little time, and that’s fair feedback. If you don’t mind me asking, I’d love to know more on where you may have gotten stuck as that’s exactly the kind of input that helps us simplify the experience further.

In the meantime, it may help to know that we have step-by-step setup guides for every supported mailer, with in-depth walkthroughs to get you up and running, and we’re always looking for ways to make these even better.
If you ever hit any snags or have suggestions on what could’ve made setup smoother, please open a thread on our support forum and we’ll be glad to help.

Kind regards

• This reply was modified 3 weeks, 4 days ago by Patrick.

Hi @sdcbmthsch,

Thanks for reaching out! I tested this on your site and wasn’t able to replicate the issue, here’s what I’m seeing on my end. Could you take a look and confirm?

In the meantime, I noticed you’re still using the legacy block to render the calendar. I’d recommend switching to the latest calendar block, either via the WordPress block editor or shortcode, as this may resolve the issue. Could you give that a try and let me know if you run into any blockers?

Looking forward to hearing from you!

Hi @janell12,

Thank you for the kind words and the honest feedback, we really appreciate it!

Glad to hear setup was smooth and that email delivery is working well for you. That’s exactly what we set out to do.

We’d love to know more about the specific features or customization options you feel are missing, that kind of feedback is genuinely useful for shaping what we work on next. WP Mail SMTP’s free version is designed to include everything you need to get your WordPress emails sending reliably, including built-in debugging and troubleshooting tools to help diagnose any delivery issues.

If something feels like it’s missing or could work better, feel free to open a support thread with more detail and we’ll be happy to take a look it’s possible what you’re looking for is already there, or we can log it as a suggestion for a future update.

Thanks again for taking the time to share your thoughts!

Hi @noahth,

I’m glad to hear it, thanks for confirming! Cheers.

Hi @123nadav,

Thanks for the update and the follow-up questions.

1. Multiple versions of Action Scheduler

When multiple plugins bundle Action Scheduler, WordPress automatically uses whichever version is the most recent one loaded. The library is designed to handle this it runs a version check on load and the newest version takes over, so you won’t end up with multiple instances running in parallel.

2. System cron + WP-Cron overlap

When you run a system cron every 5 minutes via wget, it triggers wp-cron.php directly. Meanwhile, Action Scheduler’s internal hook fires every minute through WP-Cron. If your system cron is hitting wp-cron.php while WP-Cron is also running via normal page loads, you can end up with overlapping cron runs, which causes actions to pile up and spike server activity.

Hope that helps clarify things! Let us know if anything else comes up.

Kind regards.

Hi @123nadav,

To confirm WP Mail SMTP does use the Action Scheduler library, so it does add the action_scheduler_run_queue cron hook to your site.

Here’s a bit of context on what it actually does:

Action Scheduler is a widely used background processing library, also used by WooCommerce, WPForms, All in One SEO, and many other popular plugins. By default, it hooks into WP-Cron and checks every minute to see if there are any scheduled tasks to run. The key thing to note is that it only checks, if there are no pending tasks queued, it uses very minimal resources and exits quickly.

WP Mail SMTP uses Action Scheduler specifically to handle background tasks like email logging, email reports, and other resource-intensive operations, so they don’t slow down your site’s front end.

Regarding your index.php going “crazy” in SSH after 24 hours, this is worth investigating a bit more carefully. A few things that could cause this:

1. A large backlog of queued actions: If there are many past-due actions stacking up, Action Scheduler will try to process them all, which can spike server activity. You can check this by going to WP Mail SMTP » Tools » Scheduled Actions in your WordPress dashboard and looking for a high volume of pending or failed actions.
2. Another plugin also using Action Scheduler: Since Action Scheduler is shared across plugins, if you have WooCommerce or WPForms active as well, their scheduled tasks run through the same hook. It’s worth checking which plugins’ tasks are actually filling the queue.

For a full overview of how WP Mail SMTP uses Action Scheduler, this doc may be helpful.

Hope this clears things up! Let us know if you have any other questions.

Kind regards.

Thank you so much for the kind words and the 5-star review @zamcomer! We’re thrilled to hear the setup went smoothly.