Answers.Body: <p>All you need to do is follow the documentation, as suggested by Karin.</p>
  
  <p>When you save the API key in the setup screen, the extension will make API calls to SparkPost and create a callback. Whenever a bounce occurs, SparkPost triggers this callback and CiviCRM can then process the bounce event accordingly.</p>
  
  <p>As also indicated in the documentation, only CiviMail bounces are currently processed.</p>
  
  <p>The cron job processes bounces produced when you have a return loop (ie. setup a specific SMTP mailbox to collect bounces) - it is not needed in the case of SparkPost as callbacks are much more reliable and efficient.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T18:19:11.127Z
Answers.Text: Thank you for clarifying. I followed the docs. CiviMail sends mass emails via SparkPost. SparkPost has 1 bounced email and 3 delayed emails.
  This bounced email does not show up in CiviCRM.
  How often are those callbacks made? Will it need a cron job to initiate the callback? Thx !
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-20T20:39:33.397Z
Answers.Text: The callback is made as soon as the bounce happens, no need to run a cron job. The extension only registers bounces for emails sent though CiviMail, so your bounce will not register in CiviCRM if sent otherwise (ie. Send email action, or transactional email). It might also be a 'soft bounce' (ie. mailbox full, out of office autoresponder, etc), in which case CiviCRM will not immediately put this email address on hold. Finally, the delayed emails are not considered a bounce and will not trigger any changes in CiviCRM - you just have to wait for these emails to be successfully sent.
Answers.UserDisplayName: cividesk
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-24T13:23:05.547Z
Answers.Text: Thank you for your clarifications. Everything seems to work now.
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:55:54.660Z
Answers.LastActivityDate: 2017-05-19T17:55:54.660Z
Answers.UserDisplayName: cividesk
Answers.Body: <p>Start here for background reading:
  <a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Bounce+Handling" rel="nofollow noreferrer">https://wiki.civicrm.org/confluence/display/CRMDOC/Bounce+Handling</a></p>
  
  <p>I found all I had to do was to just follow the Documentation: <a href="https://docs.civicrm.org/sparkpost/en/latest/install/" rel="nofollow noreferrer">https://docs.civicrm.org/sparkpost/en/latest/install/</a></p>
  
  <p><a href="https://i.sstatic.net/BNFbh.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/BNFbh.png" alt="enter image description here"></a></p>
  
  <p><strong>Update</strong>
  Bounces are processed through a callback (no need for an email account dedicated to bounce processing), but CiviCRM only processes bounces for CiviMail-originated emails. CiviDesk is planning to extend bounce processing to transactional emails in the future as well.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T16:21:08.063Z
Answers.Text: Hi Karin,
  Yes, I executed that cron job several times. Result according to the cron log was successful, but still no bounces recorded in CiviCRM.
  Would I need this cron job running for the rest api as well? Got the impression that communication of bounces was done using this rest api
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T16:22:59.003Z
Answers.Text: Oh, I also set up a bounce domain in SparkPost. Would that make any difference?
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:00:28.560Z
Answers.Text: That's exactly what I did.
  What kind of API key did you generate at Sparpost website?
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:03:11.290Z
Answers.Text: See my note - it can only register CiviMail bounces at the moment (not Transactional email)
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:06:42.917Z
Answers.Text: I created an API key with all permissions granted (as suggested in the doc)
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:09:02.370Z
Answers.Text: Yep did that as well :)
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:09:44.287Z
Answers.Text: And yes, I only have sent mails using CiviMail...
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T17:36:13.007Z
Answers.Text: followed the docs you mentioned.
  
  If there is no need for a dedicated email account for bounce processing because the processing is done by callbacks, there would be no reason to run the fetch_bounces Job, or am I missing something?
  
  Would I need to configure things relating to REST API in CiviCRM?
  
  Many thanks !
Answers.UserDisplayName: TonV
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-19T16:16:43.357Z
Answers.LastActivityDate: 2017-05-19T18:46:13.683Z
Answers.LastEditDate: 2017-05-19T18:46:13.683Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>I have installed the Cividesk Sparkpost extension and am able to send mass mailings with CiviMail via my Sparkpost account (REST API).</p>
  
  <p>However, CiviCRM apparently doesn't process bounces.
  Would I have to configure something else, besides the SparkPost extension?</p>
  
  <p>Any Cron Job to run?</p>
  
  <p>Many thanks
  Ton</p>
  
Tags: <civimail><rest><sparkpost>
Title: Sparkpost Cividesk integration - processing of bounces
ThreadText: # Sparkpost Cividesk integration - processing of bounces
  
  (Asked by: username_0 on 2017-05-19)
  
  I have installed the Cividesk Sparkpost extension and am able to send mass mailings with CiviMail via my Sparkpost account (REST API).
  
  However, CiviCRM apparently doesn't process bounces.
  Would I have to configure something else, besides the SparkPost extension?
  
  Any Cron Job to run?
  
  Many thanks
  Ton
  
  **Tags:** civimail, rest, sparkpost
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-05-19. Score: 1
  
  All you need to do is follow the documentation, as suggested by Karin.
  
  When you save the API key in the setup screen, the extension will make API calls to SparkPost and create a callback. Whenever a bounce occurs, SparkPost triggers this callback and CiviCRM can then process the bounce event accordingly.
  
  As also indicated in the documentation, only CiviMail bounces are currently processed.
  
  The cron job processes bounces produced when you have a return loop (ie. setup a specific SMTP mailbox to collect bounces) - it is not needed in the case of SparkPost as callbacks are much more reliable and efficient.
  
  > **Comments:**
  > **username_0**: Thank you for clarifying. I followed the docs. CiviMail sends mass emails via SparkPost. SparkPost has 1 bounced email and 3 delayed emails. This bounced email does not show up in CiviCRM. How often are those callbacks made? Will it need a cron job to initiate the callback? Thx !  
  > **username_1**: The callback is made as soon as the bounce happens, no need to run a cron job. The extension only registers bounces for emails sent though CiviMail, so your bounce will not register in CiviCRM if sent otherwise (ie. Send email action, or transactional email). It might also be a 'soft bounce' (ie. mailbox full, out of office autoresponder, etc), in which case CiviCRM will not immediately put this email address on hold. Finally, the delayed emails are not considered a bounce and will not trigger any changes in CiviCRM - you just have to wait for these emails to be successfully sent.  
  > **username_0**: Thank you for your clarifications. Everything seems to work now.  
  
  ---
  
  ### Answer by username_2 on 2017-05-19. Score: 1
  
  Start here for background reading:
  <https://wiki.civicrm.org/confluence/display/CRMDOC/Bounce+Handling>
  
  I found all I had to do was to just follow the Documentation: <https://docs.civicrm.org/sparkpost/en/latest/install/>
  
  [![enter image description here](https://i.sstatic.net/BNFbh.png)](https://i.sstatic.net/BNFbh.png)
  
  **Update**
  Bounces are processed through a callback (no need for an email account dedicated to bounce processing), but CiviCRM only processes bounces for CiviMail-originated emails. CiviDesk is planning to extend bounce processing to transactional emails in the future as well.
  
  > **Comments:**
  > **username_0**: Hi Karin, Yes, I executed that cron job several times. Result according to the cron log was successful, but still no bounces recorded in CiviCRM. Would I need this cron job running for the rest api as well? Got the impression that communication of bounces was done using this rest api  
  > **username_0**: Oh, I also set up a bounce domain in SparkPost. Would that make any difference?  
  > **username_0**: That's exactly what I did. What kind of API key did you generate at Sparpost website?  
  > **username_2**: See my note - it can only register CiviMail bounces at the moment (not Transactional email)  
  > **username_2**: I created an API key with all permissions granted (as suggested in the doc)  
  > **username_0**: Yep did that as well :)  
  > **username_0**: And yes, I only have sent mails using CiviMail...  
  > **username_0**: followed the docs you mentioned.  If there is no need for a dedicated email account for bounce processing because the processing is done by callbacks, there would be no reason to run the fetch_bounces Job, or am I missing something?  Would I need to configure things relating to REST API in CiviCRM?  Many thanks !  
  
  ---
  
  