Rate limiting the email queue

Post

Posted
Rating:
#5266 (In Topic #1192)
Avatar
Standard member
supertramp4 is in the usergroup ‘Well-settled’
Hi,

I am moving composer to a new hosting platform, and to mitigate against any potential spam blacklisting, i want to reduce the volume of e-mails being sent from the Cron_bridge e-mail queue.

Can you confirm if this file that the cron bridge actually uses to send the emails from the queue
sources/hooks/systems/cron/mail_queue.php

or are there any other files i should be aware of ?
( are forum topic notifications where e-mail rather than digest, also sent from from this mail_queue.php

The concept would be to edit this file so that for each sucessfully sent e-mail a counter is incremented. Once ( say 10 ) e-mails have been sent, then exit the mail_queue.php  loop, which therefore has to wait for the next Cron task to trigger Cron_Bridge, and thus another 10 e-mails are sent

Does this seem sensible for the initial "Warming up" phase of Spam blacklisting sites to get familiar to the new hosting site IP address.

Thanks
Chris
 
Online now: No Back to the top

Post

Posted
Rating:
#5267
Avatar
Site director
Chris Graham is in the usergroup ‘Administrators’
Yes the cron all runs through that script, and the Composr cron hooks run through Composr's cron system.

Notifications go through the mail queue (driven by the cron hook you found), assuming the mail queue option is enabled, and it sounds like it is.

So, yes to all so far.

Newsletters go through a different cron hook, which already support 'drip sending' via some config options. You could probably steal some of the code from newsletter_drip_send.php to do what you want, then re-use these config options.

I would not normally expect the Composr mail queue to send out e-mails at an alarming rate, but I know your site is a special case.


Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon

Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Online now: No Back to the top
1 guest and 0 members have just viewed this.
Back to Top