@bobinoz Yes, Comment Mail includes a queue processor that handles large numbers of outgoing emails. Comment Mail Pro includes the ability to control the queue processor (see screenshot of Queue Processor Adjustments), so that sounds like it would solve your issue quite nicely.
Basically, if you have a lot of outgoing notifications generated by Comment Mail, the queue processor handles those to control how quickly they get sent out (according to your settings). In Comment Mail Lite (the free version available here on WordPress.org), the queue processor uses the settings shown in the screenshot above, however those settings can’t be tweaked in the free version.
Regarding SparkPost: Outgoing emails can certainly be configured to use whatever SMTP email service you like (Comment Mail Pro includes a panel that allows you to configure the SMTP server used by WordPress for outgoing emails; otherwise you can use any other plugin such as WP-Mail-SMTP).
Also worth mentioning regarding SparkPost: Comment Mail Pro includes a feature that allows your subscribers to reply directly to comment notification emails to add new replies to their comments (instead of using the comment form on the post)—we call this feature Replies Via Email (RVE). We’re working on adding SparkPost support for RVE; see https://github.com/websharks/comment-mail/issues/265
Thank you for such a speedy and thorough response, much appreciated. Looks like for me that Comment Mail is the way to go, and if I do, I’ll definitely grab the pro version. I’m a bit scared about making the move over, is it really that smooth moving from StCR? Comment Mail seems to have so many settings, so I’m wondering if I would need to go through them all or would it just work straight away after the upgrade?
Also, are you suggesting that WP-Mail-SMTP plug-in would be a better option than the SparkPost plug-in? https://wordpress.org/plugins/sparkpost/
I was also wondering about the subscribers ability to answer comments directly from email, is that really such an advantage? I’m just thinking that if somebody wants to add a comment, they should at least make the effort to visit the site, otherwise there might be a tendency for people receiving notifications on their iPhones or whatever whilst they are out in the pub (for example) sending back a reply that, let’s say, didn’t have much thought behind it 🙂 Also, if they don’t need to visit the site does that mean it doesn’t count as a visitor in the stats?
So, can RVE be turned off?
is it really that smooth moving from StCR?
Yes, and the nice thing is that Comment Mail doesn’t touch your StCR database at all—it just imports all of your subscribers and leaves the StCR data in place. That way you can verify that the subscriptions imported properly, disable StCR (but not delete it), and if you discover a problem with Comment Mail (or decide you don’t like it), you can just disable Comment Mail, re-enable StCR, and things will be back to the way they were.
Comment Mail imports many StCR settings (see Subscribe to Comments Reloaded (StCR); Settings Imported by Comment Mail Upon Plugin Activation), but it’s still a good idea to go through the Comment Mail settings to become familiar with what’s available.
Also, are you suggesting that WP-Mail-SMTP plug-in would be a better option than the SparkPost plug-in?https://wordpress.org/plugins/sparkpost/
No, I’m just more familiar with WP-Mail-SMTP; SparkPost should work just fine.
can RVE be turned off
Certainly. And it’s disabled by default. The RVE feature is something that depends on your audience. Some site owners love the idea because it makes things easier for commenters. Others would rather have visitors coming to their website to leave a comment so that they expose them to other things on the site. You don’t have to use the feature if you don’t want to. 🙂
@bobinoz,
You can make sure that StCR features will work on Comment Mail without any issue. A lot of time has been dedicated to get the best of StCR and put it into Comment Mail.
Best Regards.!!
Thank you both for your help here, it sounds like you have got everything covered. I will definitely move over to Comment Mail at some point this week to see if it resolves my issues. I will let you know how it goes. Many thanks, Bob
Okay, so I took the plunge today and tried to switch over to Comment Mail, but after brief testing I think I have the same problem with emails awaiting processing that has already been discussed here…
https://github.com/websharks/comment-mail/issues/192
The comment test I tried was replying to a comment that had about 100 subscribers and after 15 minutes I still had 80 emails in the queueing system marked as ‘awaiting processing’. If I understand the default settings in the free version, which are that it runs for 30 seconds every five minutes and sends four emails per second, then all of these emails should have been sent with the first cron job run?
If this is correct and I do have this same issue, have you made any progress with it?
You were right about how easy it was to switch back to StCR though, that’s what I’ve done now and all my settings were saved and it’s working okay, but obviously I still have the original problem so it would be nice to fix this awaiting processing issue.
Thanks in advance for any help any of you can give me here.
@bobinoz We’ve been having some trouble reproducing the issue described in the GitHub issue you linked to, and that’s making it difficult to pinpoint what the cause is. However, your report makes 3 cases of this so far, so it’s definitely an issue.
If you could leave a comment on the GitHub issue with a list of your active plugins, that would be a huge help. My only guess at this point is that there’s another plugin conflicting with Comment Mail, because we haven’t been able to reproduce the issue in a clean WordPress install with only Comment Mail running.
I’ll also add a link back to this thread in the GitHub issue.
Thanks raamdev, I’ve just added the information you have asked for over at Github.
