Hi, batch means something else…
Here are the options:
Limit number of messages sent at a time. Defaults to value set in config.
Limit the number of seconds per batch. Defaults to value set in config.
By default, failed messages older than the --recover-timeout setting will be attempted one more time then deleted if it fails again. If this is set, sending of failed messages will continue to be attempted.
Sets the amount of time in seconds before attempting to resend failed messages. Defaults to value set in config.
Sets the amount of time in seconds before deleting failed messages. Defaults to value set in config.
Set name of lock to run multiple mautic:emails:send command at time
Force execution even if another process is assumed running.
If getmypid() is disabled on this system, lock files will be used. This option will assume the process is dead after the specified number of seconds and will execute anyway. This is disabled by default. [default: false]
Allowed value are “pid” , “file_lock” or “flock”. By default, lock will try with pid, if not available will use file system [default: “pid”]
Display this help message
Do not output any message
Display this application version
Force ANSI output
Disable ANSI output
Do not ask any interactive question
The Environment name. [default: “prod”]
Switches off debug mode.
Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
Probably you won’t exeed 14/sec, you would need a powerful server for that.
If you want to send max 14 / sec, limit your –message-limit=840 and run it every minute.
Also, no I’m actually not running any of these cron jobs every minute.
So far I’ve been running mautic:broadcasts:send --batch=13 every 5 minutes, which i see is needed for broadcast emails, then after that I guess mautic:messages:send runs to send out those 13 emails that were just taken from the broadcast batch?
So really the final limit argument; so as to not go against my SES limit, should really be set on mautic:messages:send ?
From the docs this is what it says about the -batch flag on broadcast emails:
--batch=X controls how many emails processed in each batch. This can be different for every provider. For example, Mautic has API connection to SparkPost. Their API can send - at present - 1000 emails per call. Therefore the batch should be 1000 for the fastest sending speed with this provider. Many SMTP providers can’t handle 1000 emails in one batch, so this would need to be lower.
It specifically talks about services not being able to “handle” the requests, by that I took to mean services not “willing” to handle the requests, which in this case is 14 per second for my SES account