I have my "maximum send time" set to 2 seconds. When I create a newsletter node and choose to send it upon submitting, my installation sent the first 9 records in the sn_subscriptions table (I checked via phpmyadmin).

Upon the next cron run, the message processing queue was restarted, but it is not sending in "2-second" batches, but rather all at once. I can see that this is happening by running the following query in phpmyadmin and seeing the results increase in number upon each refresh.

SQL-query: 
SELECT *
FROM `sn_subscriptions`
WHERE s_status =1
LIMIT 0 , 30

The record count is still climbing incrementally, even 5+ minutes following my call to cron.php.

I don't know whether to categorize this behavior under "intended," "feature request" or "bug report," but I believe that the "maximum send time" should be obeyed even if sending by cron.

Comments

DriesK’s picture

DriesK commented
Priority: Critical » Normal
Status: Active » Closed (works as designed)

This is "by design". The "maximum send time" setting is only there for the initial send, that is, when the newsletter is actually sent. Further sending is handled by cron, and from that point on, it is up to Drupal to decide how to manage its cron jobs.

However, the development of a separate mail.inc is currently being initiated. This engine will not only be used by simplenews, but by all mail sending modules, and it will (probably) have a setting for the maximum number of emails sent per cron run. It is obviously better that this is handled on a centralized way, instead of each module having its own implementation.