CiviCRM Community Forums (archive)

I have setup my civimail.cron.php as per the manual to trigger every 5 minutes.  I also setup my Mailer Spool Period in the Mailer Settings for 7200 seconds(2hours) and the Mailer Batch Limit to 350, as the host I am sending my mail through only allows 400 emails per hour.

When I send a scheduled mailing that is over 350 users, the job gets executed on the next cronjob, pauses the batch after 350 emails, but then instead of waiting for 2 hours to continue the batch, it starts up again on the next cronjob...5 minutes later.  So I end up exceeding my mail hosts limit, and getting bounces for everything over their 400/hr limit.

Did I miss something in my setup?  Is there a way for civimail or civimail.cron.php to recognize that a batch is in progress and not trigger it to send before its time?

I have searched the forum on this, and have seen others ask similar and even same questions, however I have not seen a solution yet.  Sorry if I missed it somewhere.  If you can point me to the link Id be grateful.

Thanks.

Thats too bad.  It seemed like such a good idea, especially under the circumstances of the host limiting the number of mails sent per hour.

I guess I will adjust the cronjob to run hourly and live with the potential of waiting for an hour when sending immediately.

Thank you for your response, I appreciate it.

shawn