SparkPost

Hi @joekissell,

If you use the HTTP API option, you can use the “wpsp_request_body” hook. Insert the following snippet in your WordPress theme (i.e. wp-config.php) and replace ‘my-pool-id’ with your IP pool id.

function set_ip_pool($body) {
  $body['options']['ip_pool'] = 'my-pool-id';
  return $body;
}

add_filter('wpsp_request_body', 'set_ip_pool');

Hi @rintesh,

This might have been related to our service issue over the weekend,?see https://status.sparkpost.com/. Either way, this does not appear to be a plugin related issue, so I am going to close this thread. If you continue to have service issues, please sign in at https://app.sparkpost.com and file a support ticket.

Thank you and have a great day!

Hi @rehhoff,
Thank for reporting this issue. A patch was released yesterday. Please upgrade to v3.2.2.

Hi @bluesix,

We are excited you signed up for an account! This appears to be a general support issue that is not specific to this plugin. Please login to our application at https://app.sparkpost.com and submit a support ticket.

Hi Simon, the changes to our Transmissions API has been pushed back from November 17, 2018, to January 12, 2019. The plugin will continue to work correctly after these changes are made.

Hey @backpackingseries, hope some of these answers help:

1) While the SparkPost plugin works well with many other plugins, it’s not something we actively test or guarantee. However, in general, any plugins that use WordPress’s official APIs to send emails should work fine with SparkPost plugin.

2) When enabled, SparkPost marks all emails sent by this plugin as transactional. SparkPost and email inbox providers sometimes treat transaction and non-transactional emails differently under the hood, for more info see: https://www.sparkpost.com/resources/infographics/email-difference-transactional-vs-commercial-emails/
If you intend to mainly sent marketing and newsletter emails, uncheck the option. While you’d generally expect emails that land in the promotions folder to not be transactional, we can’t really say what makes a specific email land there. If you are sending a mix of transactional and marketing emails, we’d suggest using Templates and saving the setting there.

3) No, it doesn’t itself depend on any cron.

4) This is normal, the plugin uses it.

5) You can disable link tracking globally in your SparkPost account or in the plugin. From the “Overrides” tab, uncheck ‘Enable Tracking’. If you want to track some emails and not others, we’d suggest using Templates and enabling it there. At the moment there isn’t a way to shorten links.

6) These types of headers are normally added to non-transactional emails for internal SparkPost and inbox provider use. Some inbox providers use them to build promotional email unsubscribe functionality. Sending your emails as transactional should remove them.

Thanks for your feedback. Looks like WordPress has API to detect when a plugin is uninstalled. We can move the option deletion logic there which will prevent this from happening.