Answers.Body: <p>I have two outside ideas that 'might' be helpful:</p>
  
  <ol>
  <li>Is it possible Activities have been made for the emails that should have gone out? Emails from the Contact record will almost certainly have created an activity, and it's a commonly set option for emails sent via Scheduled reminders. If an activity has been made it will probably contain the email.</li>
  <li>Do you have email logging turned on? Presumably not or you wouldn't be asking the question! But perhaps worth checking...</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-22T14:49:28.677Z
Answers.Text: Thanks, I was hoping the extension may have maintained a queue or log of messages that couldn't be sent but I haven't found evidence of this, so it's a matter of doing detective work to figure out what should have been sent.
  By email logging, did you mean CIVICRM_MAIL_LOG or mail server logging? CIVICRM_MAIL_LOG was off and the mail server doesn't see the messages as they are submitted by the extension directly to Sparkpost using their API.
Answers.UserDisplayName: davejenx
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-22T19:34:42.310Z
Answers.Text: Re email logging - I meant both of those possibilities. Sorry they aren't able to help and I wish I had further ideas to offer. :(
Answers.UserDisplayName: Andyg8
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-23T11:39:20.813Z
Answers.Text: Thanks, I believe the end user has now tracked down what needed to be re-sent.
Answers.UserDisplayName: davejenx
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-11T20:02:17.323Z
Answers.LastActivityDate: 2017-08-11T20:02:17.323Z
Answers.UserDisplayName: Andyg8
Body: <p>Have been using the com.cividesk.email.sparkpost extension (v1.1) successfully on Civi 4.6.30 . Recently had an issue due to installing PHP mcrypt on the server, which caused the extension to be unable to retrieve the SparkPost API key. [More accurately: the call to <code>CRM_Sparkpost::getSetting('sparkpost_apiKey')</code> was returning a scrambled value.] This was resolved, once the problem was diagnosed, by re-entering the API key. (I've written a <a href="https://civicrm.stackexchange.com/questions/19914/why-does-outbound-email-stop-working-after-enabling-the-php-mcrypt-extension">separate Q&amp;A about that issue</a>, as it's not SparkPost specific.)</p>
  
  <p>During the time when the API key couldn't be accessed, numerous transactional emails and CiviMails should have gone out. The CiviMails can be re-sent easily enough but what's the way to deal with the transactional emails? There's no record in the extension's log file of mails that attempted to send during this period. Is there any queueing system for failed messages? Because the API key couldn't be correctly retrieved, presumably the messages won't have been linked to the user's SparkPost account. The SparkPost stats show no messages over that period.</p>
  
Tags: <sparkpost>
Title: Is there a way to re-send failed transactional emails using SparkPost email extension?
ThreadText: # Is there a way to re-send failed transactional emails using SparkPost email extension?
  
  (Asked by: username_0 on 2017-08-10)
  
  Have been using the com.cividesk.email.sparkpost extension (v1.1) successfully on Civi 4.6.30 . Recently had an issue due to installing PHP mcrypt on the server, which caused the extension to be unable to retrieve the SparkPost API key. [More accurately: the call to `CRM_Sparkpost::getSetting('sparkpost_apiKey')` was returning a scrambled value.] This was resolved, once the problem was diagnosed, by re-entering the API key. (I've written a [separate Q&A about that issue](https://civicrm.stackexchange.com/questions/19914/why-does-outbound-email-stop-working-after-enabling-the-php-mcrypt-extension), as it's not SparkPost specific.)
  
  During the time when the API key couldn't be accessed, numerous transactional emails and CiviMails should have gone out. The CiviMails can be re-sent easily enough but what's the way to deal with the transactional emails? There's no record in the extension's log file of mails that attempted to send during this period. Is there any queueing system for failed messages? Because the API key couldn't be correctly retrieved, presumably the messages won't have been linked to the user's SparkPost account. The SparkPost stats show no messages over that period.
  
  **Tags:** sparkpost
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-08-11. Score: 2
  
  I have two outside ideas that 'might' be helpful:
  
  1. Is it possible Activities have been made for the emails that should have gone out? Emails from the Contact record will almost certainly have created an activity, and it's a commonly set option for emails sent via Scheduled reminders. If an activity has been made it will probably contain the email.
  2. Do you have email logging turned on? Presumably not or you wouldn't be asking the question! But perhaps worth checking...
  
  > **Comments:**
  > **username_0**: Thanks, I was hoping the extension may have maintained a queue or log of messages that couldn't be sent but I haven't found evidence of this, so it's a matter of doing detective work to figure out what should have been sent. By email logging, did you mean CIVICRM_MAIL_LOG or mail server logging? CIVICRM_MAIL_LOG was off and the mail server doesn't see the messages as they are submitted by the extension directly to Sparkpost using their API.  
  > **username_1**: Re email logging - I meant both of those possibilities. Sorry they aren't able to help and I wish I had further ideas to offer. :(  
  > **username_0**: Thanks, I believe the end user has now tracked down what needed to be re-sent.  
  
  ---
  
  