devot:eeDevoted to ExpressionEngine

I don’t think I’m fully understanding what’s going on with this plugin.

the EE email settings determine how many emails can be sent per hour.

the FM settings determine how many is sent in a batch.

So when I have a list of 10,000 subscribers and a limit of 500 per hour, I do what?

If I select “send first batch (100)”, It sends out 100. However I don’t see any way to send a second? If I click back into it, I still see “send first batch”. If I click that it sends a completely new email.

If I say send all batches, It just automatically tries to process all 10,000 emails.

How exactly are we meant to manage lists with large numbers and sending restrictions?

the FM settings determine how many is sent in a batch.

yes, this is correct

the EE email settings determine how many emails can be sent per hour.

no, the EE email settings contain a setting called “Number of Emails Per Batch” but this is overwritten by the FM settings.

If I select “send first batch (100)”, It sends out 100. However I don’t see any way to send a second? If I click back into it, I still see “send first batch”. If I click that it sends a completely new email.

on the main add-on page you should see the status of your email set to “Incomplete”, and below it a “Send Next Batch”. clicking on it will only send the next batch.

How exactly are we meant to manage lists with large numbers and sending restrictions?

if you have an hourly limit of 500 then you could set the batch size to 100 and send 5 batches, one at a time, per hour.

let me know if anything is still unclear

Thanks for your reply.

“on the main add-on page you should see the status of your email set to “Incomplete”, and below it a “Send Next Batch”. clicking on it will only send the next batch.”

I think this is the problem. I don’t see send next batch at all. I only ever see “send all batches”

I have set up a test with 10 addresses and a batch limit of 1. Same thing happens every time. Same for a limit of 2.

setting batch mode to “on” in email settings should fix this. also version 2.1.3 contains a bugfix that solves this so i’d recommend updating.

ok great. Thanks.