You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On September 1, 2020, SparkPost will be deprecating TLSv1.1 fallback across all of our systems. This is an older security standard for sending email and contains vulnerabilities that directly impact the integrity and security of your communications; vulnerabilities which cannot be fixed in these older implementations.
As long as connections are made using TLSv1.2, this change will result in zero impact to your ongoing use of our service; however if connections are made using TLSv1.1, you will observe a failure to connect to API and SMTP endpoints. To ensure that there is no impact to existing processes, it is best to verify that your clients support TLSv1.2. You can verify the version of TLS that your client is using by collecting local packet captures of network traffic and inspecting which version of TLS is being used to establish a secure connection to SparkPost (handshake).
If you are using TLSv1.1, then you should take the following steps:
If you are using proprietary code, have your in-house development team update the code to use TLSv1.2.
If you are using 3rd party software, verify that your client supports TLSv1.2, and upgrade the client.
Do you have any idea if sparkpost_rails is using TLS > v1.2 ? Sorry if my question is not relevant, I'm not sure do understand very nice this protocol thing...
The text was updated successfully, but these errors were encountered:
Hi there ! I received this email from Sparkpost
Do you have any idea if sparkpost_rails is using TLS > v1.2 ? Sorry if my question is not relevant, I'm not sure do understand very nice this protocol thing...
The text was updated successfully, but these errors were encountered: