Title: SparkPost's Replies | WordPress.org

---

# SparkPost

  [  ](https://wordpress.org/support/users/sparkpost/)

 *   [Profile](https://wordpress.org/support/users/sparkpost/)
 *   [Topics Started](https://wordpress.org/support/users/sparkpost/topics/)
 *   [Replies Created](https://wordpress.org/support/users/sparkpost/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/sparkpost/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/sparkpost/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/sparkpost/engagements/)
 *   [Favorites](https://wordpress.org/support/users/sparkpost/favorites/)

 Search replies:

## Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] Selecting IP Pool](https://wordpress.org/support/topic/selecting-ip-pool/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [5 years, 5 months ago](https://wordpress.org/support/topic/selecting-ip-pool/#post-13814755)
 * Hi [@joekissell](https://wordpress.org/support/users/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');
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] Plugin not sending email](https://wordpress.org/support/topic/plugin-not-sending-email-4/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/plugin-not-sending-email-4/#post-13668716)
 * Hi [@rintesh](https://wordpress.org/support/users/rintesh/),
 * This might have been related to our service issue over the weekend, see [https://status.sparkpost.com/](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](https://app.sparkpost.com) and file a support 
   ticket.
 * Thank you and have a great day!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] WP 5.5 – PHPMailer Deprecated Notice](https://wordpress.org/support/topic/wp-5-5-phpmailer-deprecated-notice/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wp-5-5-phpmailer-deprecated-notice/#post-13345125)
 * Hi [@rehhoff](https://wordpress.org/support/users/rehhoff/),
    Thank for reporting
   this issue. A patch was released yesterday. Please upgrade to v3.2.2.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] Can’t send via HTTP or SMTP “Authentication credentials invalid”](https://wordpress.org/support/topic/cant-send-via-http-or-smtp-authentication-credentials-invalid/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/cant-send-via-http-or-smtp-authentication-credentials-invalid/#post-13275595)
 * Hi [@bluesix](https://wordpress.org/support/users/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](https://app.sparkpost.com) and submit a support ticket.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] Changes to Error Handling in Transmissions API](https://wordpress.org/support/topic/changes-to-error-handling-in-transmissions-api/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/changes-to-error-handling-in-transmissions-api/#post-10827376)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SparkPost] Plugin features](https://wordpress.org/support/topic/plugin-features-15/)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/plugin-features-15/#post-10641057)
 * Hey [@backpackingseries](https://wordpress.org/support/users/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/](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.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[SparkPost] Settings gone](https://wordpress.org/support/?post_type=topic&p=9507731)
 *  Plugin Author [SparkPost](https://wordpress.org/support/users/sparkpost/)
 * (@sparkpost)
 * [8 years, 8 months ago](https://wordpress.org/support/?post_type=topic&p=9507731#post-9560672)
 * 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.

Viewing 7 replies - 1 through 7 (of 7 total)