Newsletter made simple - Hosts email quota limits emails per hour

[pb4sc]

Hi,
  I need some help with Newsletter made simple.  My customer has 1600 signups for his newsletter.  The problem is my host.  They only allow 500 emails per hour max.  My question is when I process a job, do I have to do it in batches of 500 over 3+ hours?  Or is there a way I can process the job, but have NMS restrict how many emails go out over an hour?  If someone can point me in the right direction, I would appreciate it.

Thanks,
pb4sc

[Ted]

Because of the nature of PHP, the job has to be running inside of your web browser and within a certain timeout limit.  Therefore, there'd be no way to be able to automatically call code like that an hour later.

The way around that would be some sort of manual process where when you process a job, you could enter the # of emails to send.  It would do those, and then the job would sit partway done until you manually sent off another chunk of the emails.

You cold possibly contact calguy and see if he would interested in doing a modification.    Your other options are something like an external email sending service (like Postini), Or, you may have to look into using an email blast service like Mailchimp or Constant Contact.

[kermit]

it could be done.. but would take some work...

need to be able to set nms to send only xx number of mails when a job is run, then automatically pause it.  log and/or send to admin the results of these automated 'batches' instead of presenting on screen...

needs some sort of "cron" support... e.g. a predefined url that you set a cron job up to hit every hour (or whatever). that url would run code that checks for in-progress jobs and runs a 'batch' if found... as an alternative to cron, some front-end code could be added that does pretty much the same thing, and with the same limits (e.g. check on every pageview, but don't actually do anything any more often than the preset limit). if using front-end code instead of true cron job, then the xx to send per batch would need to be pretty small, so it doesn't slow down the front-end too much

but at 1600 mails (and presumably growing), i'd probably start looking at a third-party service.. or a change in hosting environment so you have more control over things like outbound mail volume and php script execution times.