CiviCRM Community Forums (archive)

In general you would set it to how many jobs in parallel you want trying to deliver one mailing. In some cases it depends on how many smtp connections your smtp provider allows. It also depends on the mailing size.

Basically number of jobs comes into play ONLY when your cronjob is fired more often than it takes to process one single job. If you are not sending a lot of mail on a constant basis, leaving the default value (i.e. 1 job) is recommened

lobo

How about

#jobs = 10
cronjob fired every 3 minutes (u can reduce this to try to get more speed)

Note that this will put a fair load on your server and civismtp connections, so i would chat with them and ensure they are fine with it

lobo

the documentation is right, the job size indicates the number of emails that should be in each job

in general splitting a mailing into multiple smaller jobs allows an install to potentially have multiple threads each working on a different sub-job

in general if you want high speed, you probably dont want to set a batch limit (i.e. u want each thread to send as many emails as quickly as possible)

we currently dont restrict the number of threads that can be run in parallel, you'll need to modify civimail.cronjob.php to do so

lobo