Topic

Just installed this plugin – and it seems great. Yet, I can’t find any documentation, in particular about how to set up the timing of the queue.

My ISP gives me a maximum of 100 messages sent per hour via SMTP.
Ideally, I would like to send everything as fast as possible – until 80 mails in an hour are reached. Then, I’d like it to wait for an hour.

Alternatively, I would like it to send one email every 45 seconds. That would always keep me under my limit.
With those three parameters… Cron job frequency, job length, and email per job… how can I set that up in GD Mail Queue?

Typically, I will run into the situation only once a year – when WooCommerce processes membership renewal reminders – but those of course are some of the most critical messages to go out, and I don’t want them to get stuck…

Thanks for any hints!

Topic Information

Topic Type:

PHP Version:

WordPress Version:

Plugin Version:

Demo URL:

Replies

Hi,

Right now there is no way to set it exactly the way you want. I plan to add some enhancements to the queue setup, where you can configure a number of emails allowed by the hosting company, and the plugin can be flexible to fit the sending into these limits. Right now, the plan is to introduce such a feature after the Summer.

The best way to around ISP or hosting limits for SMTP is to use REST API for third-party email services (Gmail, Amazon SES, MailGun…). Emails sent via REST API don’t have anything to do with SMTP protocol. But, you would need to have an account with one of the services (many have free plans for low volume of emails sent). GD Mail Queue Pro has support for several services using REST API: Amazon SES, Gmail, MailGun, SendGrid, MailJet, and SendInBlue (to be released on Monday).

Regards,
Milan

Dev4Press - Premium plugins for WordPress.

1 user thanked author for this post.

baylands

Thanks a lot! I guess I’ll wait for your update then, I still have a few months until I need this. REST API? Yes, I am reading this all the time – but did not (yet) have the intention to dive into it more deeply…

Hello Milan –

“Right now, the plan is to introduce such a feature after the Summer.”

Any idea about an ETA for this? (I’m trying to get my site ready for membership renewal season, starting at the end of September, which will be the only time of the year when I have the email quantity problem…)

Thanks a lot!

Georg

Hi,

I planned to work on this already, but, the timeline has changed due to the unplanned work needed for WordPress 5.5 and very important core change WP introduced related to the mail system. Plugin version 5.1 was released recently, and in the first half of September, 5.2 will be out with more changes related to WordPress 5.5. Because of that, most of the things planned for September and October have been pushed back. Changes in WordPress required (and still requires) prolonged testing that delays any new development.

The feature we talked about was planned for after the Summer, but that was a literal date based plan, Summer ends in late September, and the plugin that will get this feature was always on track for late September or early October. WordPress 5.5 did change some stuff, so the release might be delayed by a few weeks to mid or late October.

Regards,
Milan

Dev4Press - Premium plugins for WordPress.

Hello Milan –

Still working on getting this all set up… and since the official feature is now delayed a bit…

A question:
If I set the “CRON job interval” to 1 minute
and the “Emails per job” to 1:

Does that mean that, if my WooCommerce Subscription generates 200 emails in one go, these 200 emails will be sent out one per minute = 60 per hour, or about 3 1/2 hours for the whole process?
(this is something that would work for me…. I know you don’t recommend to run the CRON job that often – but… there isn’t all that much going on on my site to overwhelm anything).

Thanks a lot!

Georg

Hi,

WordPress doesn’t recommend running CRON that often. But, in my experience, most hosting companies and even the worse shared accounts can deal with emails if you don’t send too many of them. So, setting CRON to 3 or 5 minutes, and sending 10 emails at the time, should work. The only way to know what you hosting can handle is to test it.

Also, the Pro version includes support for various REST API based email services, and they don’t use normal hosting SMTP to send emails, and they don’t have any limits imposed, because emails are sent via REST API. But, you need to have an account on one of the supported services (Amazon SES, SendGrid, MailJet, Mailgun, SendInPulse, Gmail). Considering different hosting services, the REST API solution is better when you need to deal with server limitations.

Anyway, the next major update will include more flexible email sending controls.

Milan

Dev4Press - Premium plugins for WordPress.

Thanks a lot for the hints about timing – SMTP works very well for me, my only problem is that I have a limit of 100 mails per hour.

Running the cron job less frequently gives me the problem that I don’t want to have people who reset their password wait 3 or 5 minutes for the reset email, – or have people wait 5 minutes for a confirmation email after making a purchase. My only mass-email that can cause a problem is the annual subscription renewal – which will hit about 250 people in a very short time frame..

Georg

New update should be ready in about a month or so, but I can’t guarantee the exact date, it can be delayed, depending on testing.

Dev4Press - Premium plugins for WordPress.