Answers.Body: <p>I'm not familiar with Office365 Relay, a quick search indicates it's for devices to send emails via Office365. It was a quick search so I may be wrong. </p>
  
  <p>Given that you are only able to send 30 emails at a time and that Office365 has a 30 emails/minute limit sounds like it is something to do with Office365 not a CiviCRM setting issue.</p>
  
  <p>You may want to look at a SMTP service, here's a <a href="https://civicrm.org/blog/andrewhunt/alternatives-to-mandrill">blog post</a> that compares some services that work with CiviCRM.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-04T14:04:19.870Z
Answers.Text: The reason I don't think it is the 30/minute limit is because if I set the cron to run every 20 seconds, it sends 90/minute.
Answers.UserDisplayName: Sebastian
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-03T22:28:47.247Z
Answers.LastActivityDate: 2016-05-03T22:28:47.247Z
Answers.UserDisplayName: Sanjay Jain
Answers.Body: <p>Sanjay is right to suggest a SMTP service.  That said, you mentioned the <strong>Mailer Batch Limit</strong> in <strong>Administer > CiviMail > Mailer Settings</strong>.  That will limit each cron run to only sending that number of emails.  A site might have a batch limit of 200, for example; that would mean that 200 messages go out on each run of the scheduled job.</p>
  
  <p>If you were setting up CiviCRM to stay within Office365's limit of 30 emails per minute, you might want to set that batch limit to 30.</p>
  
  <p>Running cron multiple times a minute may defeat Office365's limit, but there are two risks:</p>
  
  <ul>
  <li>you may have cron double up on itself (it's not unrealistic for cron to take over 20 seconds)</li>
  <li>you might get summarily dumped by Office365 for violating their terms of service, causing a big disruption</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-09T17:00:10.773Z
Answers.LastActivityDate: 2016-05-09T17:05:56.883Z
Answers.LastEditDate: 2016-05-09T17:05:56.883Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I'm having an issue with CiviMail.  When the cron runs to send the scheduled mail it only sends 30 emails at a time.  I have it set up to send through Office365 SMTP Relay, so its not the 30 messages a minute limit that Office365 has.  I have the batch limit set to unlimited, so its not that either.</p>
  
  <p>I can't find anything in the files that would be limiting it to only 30 messages per cron run.</p>
  
  <p>My mailing list has about 5000 people in it, and I need to be able to send them all quickly.  At 30 a minute it takes 3 hours, which isn't going to work.  I even set up my cron to run every 20 secs to speed it up to an hour for all the messages. I can speed it up even more if I lower the time between runs, but I shouldn't have to.  I should be able to either send them all to Office365 or in large batches and have them send quicker than it is allowing me too. </p>
  
  <p>Any ideas?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-04T00:21:21.437Z
Comments.Text: In my experience, 5000 is high to be sending via your regular email provider. I would seriously consider a third party SMTP or mail distribution service.
Comments.UserDisplayName: choster
Tags: <civimail>
Title: Why is Civimail sending exactly 30 emails every cron run through Office365 SMTP Relay?
ThreadText: # Why is Civimail sending exactly 30 emails every cron run through Office365 SMTP Relay?
  
  (Asked by: username_0 on 2016-05-03)
  
  I'm having an issue with CiviMail. When the cron runs to send the scheduled mail it only sends 30 emails at a time. I have it set up to send through Office365 SMTP Relay, so its not the 30 messages a minute limit that Office365 has. I have the batch limit set to unlimited, so its not that either.
  
  I can't find anything in the files that would be limiting it to only 30 messages per cron run.
  
  My mailing list has about 5000 people in it, and I need to be able to send them all quickly. At 30 a minute it takes 3 hours, which isn't going to work. I even set up my cron to run every 20 secs to speed it up to an hour for all the messages. I can speed it up even more if I lower the time between runs, but I shouldn't have to. I should be able to either send them all to Office365 or in large batches and have them send quicker than it is allowing me too.
  
  Any ideas?
  
  **Tags:** civimail
  
  > **Comments:**
  > **username_1**: In my experience, 5000 is high to be sending via your regular email provider. I would seriously consider a third party SMTP or mail distribution service.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-05-03. Score: 5
  
  I'm not familiar with Office365 Relay, a quick search indicates it's for devices to send emails via Office365. It was a quick search so I may be wrong.
  
  Given that you are only able to send 30 emails at a time and that Office365 has a 30 emails/minute limit sounds like it is something to do with Office365 not a CiviCRM setting issue.
  
  You may want to look at a SMTP service, here's a [blog post](https://civicrm.org/blog/andrewhunt/alternatives-to-mandrill) that compares some services that work with CiviCRM.
  
  > **Comments:**
  > **username_0**: The reason I don't think it is the 30/minute limit is because if I set the cron to run every 20 seconds, it sends 90/minute.  
  
  ---
  
  ### Answer by username_3 on 2016-05-09. Score: 0
  
  username_2 is right to suggest a SMTP service. That said, you mentioned the **Mailer Batch Limit** in **Administer > CiviMail > Mailer Settings**. That will limit each cron run to only sending that number of emails. A site might have a batch limit of 200, for example; that would mean that 200 messages go out on each run of the scheduled job.
  
  If you were setting up CiviCRM to stay within Office365's limit of 30 emails per minute, you might want to set that batch limit to 30.
  
  Running cron multiple times a minute may defeat Office365's limit, but there are two risks:
  
  * you may have cron double up on itself (it's not unrealistic for cron to take over 20 seconds)
  * you might get summarily dumped by Office365 for violating their terms of service, causing a big disruption
  
  
  ---
  
  