A few days ago I noticed that my Flarum installation was producing errors on many actions such as new account registration and posting replies. Turning on debug mode revealed the error Unable to connect with TLS encryption.
I've been successfully using Sparkpost as my SMTP provider, and since nothing had changed recently on my server or Flarum installation, I figured maybe something changed with Sparkpost. And indeed, I recalled getting an email from Sparkpost about TLSv1.0 getting deprecated. Here's the email:
Hello,
You are receiving this operational notification because you have a SparkPost account.
We previously announced that SparkPost will deprecate TLSv1.0 on June 30. We have extended this date to July 9 in order to give some customers additional time to update their injection code to use a newer protocol: TLSv1.1 or TLSv1.2.
We are deprecating TSLv1.0 in order to meet an important industry-wide security standard. Starting on July 9, all API calls made to SparkPost must use TLSv1.1 or higher or they will fail with an authentication error.
In an effort to help our customers with the transition, we’ve set up test endpoints that will reject any API calls that do not use TLSv1.1 or higher. You can use these endpoints to inject email traffic (or make other API calls) using your current software. If it's on TLSv1.0, the traffic will be rejected. If it's on TLSv1.1, the traffic will be accepted. These endpoints are described in this support article.
We are working hard to make sure the transition is a smooth one.
Is it possible this deprecation of TLSv1.0 is what has caused my Flarum's email sending to stop working?
For now I have switched to Amazon SES which seems to still be working fine, but it'd be nice to be able to switch back to Sparkpost since that's slightly cheaper for my usage levels.