SparkPost API change - anyone know if this will affect service for Discourse?


#1

They are amending the API on Monday, does anyone have a 5 mile high view on whether Discourse sites that use SparkPost will be affected?:

" As a reminder, and as outlined in this blog post, we will make suppression checks asynchronously on incoming messages. As a result, the response in both the REST Transmissions API and the SMTP API will change as follows:

SMTP API

  • Current: return a ‘250 Ok’ and ‘policy rejection’ event (no injection event)

  • Future: return a ‘250 Ok’ with ‘injection’ event followed by a ‘bounce’ event

Transmissions REST API

Single recipient

  • Current: return a 400 with special error message, followed by a ‘generation rejection’ event

  • Future: return a 200 with an ‘injection’ event followed by a ‘bounce’ event

Multiple recipient

  • Current: return a 200 followed by a ‘generation rejection’ event (no injection event)

  • Future: return a 200 with an ‘injection’ event followed by a ‘bounce’ event

When a bounce is generated due to suppression, the webhook will have bounce_class of “25” and an error_code of “554” and reason of “Recipient address was suppressed due to customer policy” or “Recipient address was suppressed due to system policy”."


(Jay Pfaffman) #2

You’re sending via smtp, not the API, right? So the API doesn’t matter.


#3

Ah Thanks. Wasn’t sure if what they mean by “SMTP API” is their SMTP interface … forgive me, not an expert and didn’t know what discourse is doing under the hood with the SMTP credentials …

Ah, this could be a good description of the difference: