Sparkpost new requirement for TLSv1.1 or TLSv1.2 - What to do?

B

brunoa

Member
Looks like using Sparkpost to send mail on Xenforo will stop working next monday, 9. What are the alternatives now? Is there any way to comply with the new their TLSv1.1/1.2 requirement?
 
brunoa said:
Looks like using Sparkpost to send mail on Xenforo will stop working next monday, 9. What are the alternatives now? Is there any way to comply with the new their TLSv1.1/1.2 requirement?
Click to expand...
Did you try AWS's SES?
 
Well, elasticmail adds your physical address and unsubscribe link to email footer. It seems you can't remove it. Damn...
 
joroom said:
AWS SES cost is 1usd for 10,000 email sent. So pretty cheap and very reliable
Click to expand...
We sent out an email to our entire member base, think it was approx 15k emails sent, with Amazon SES recently.

We had about 1.3k bounces, which got us into trouble, but that's because I hadn't properly cleaned the mailing list of old spam accounts etc prior to sending the newsletter.

Anyway, my point is our first bill came the other day, a whole £0.02 ($0.03). Such bill, much poor, lv100 fees, wow :P

In short, Amazon SES is indeed cheap and reliable, although they are very strict in maintaining a clean mailing list. The upside to this is that their support tickets are read by humans, and their replies show they read 100% of what you actually write and make a human decision based on what you actually told them. I was very impressed by that, especially considering they are larger than even PayPal, and if you tell me you've received a helpful reply from PayPal customer support I'm going to call you a liar :P


Fillip
 
Will XF get support for TLSv1.1/1.2? Maybe I'll take a look at Amazon SES. Elasticmail is great, but hate their required footer.

Just recall of another one I used to use: https://www.mailgun.com
 
Last edited:
AWS SES is cheap, and I use it for one of my forums. But, Sparkpost's API is really good, and I can't complain one bit about their free tier.

The question is, how we can make XF2 work with TLS v1.1/1.2?
 
I don't have any complaints about Sparkpost either. I'd like to use it, but I guess it's a no go. I forgot a little about that thing with Sparkpost and need to find something urgently.
 
I've changed the following code, and testing with Sparkposts endpoint as defined here, it seems to work:

https://www.sparkpost.com/docs/tech-resources/tlsv1-0-test-hostname/

NOTE: THIS IS FOR XF2 ONLY!

File: /src/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport (Line 95)

Find:
PHP: 
return stream_socket_enable_crypto($this->_stream, true, STREAM_CRYPTO_METHOD_TLS_CLIENT);

Change to:
Code: 
return stream_socket_enable_crypto($this->_stream, true, STREAM_CRYPTO_METHOD_TLSv1_1_CLIENT);

Seems to work for me, before I was getting the TLS error in the sever error logs, now it's going through and I can see the entry in the sparkpost dashboard:

sparkposttest.webp

I'll continue with more testing today.
 
It seems to be working for me as I'm able to send emails adhoc, and I see some in the logs in Sparkpost. Are you using XF 2? Also, your server would need to have TLS 1.1 to use that I believe.

What's the server error?
 
Yes, I'm on XF2, not sure about the TLS 1.1 on my server, already deleted server error... Currently trying another service... If it works out well, then I'm good.

Thanks for now.
 
No problem. This XF2 site I tested on is using PHP 7.1.19 on CentOS 7 (Apache as well).

I have one other site using 1.5 and Sparkpost, so I might move it to Amazon SES until I get this site moved to XF2.
 
You must log in or register to reply here.
Back
Top Bottom