EOF caught while checking if connected

  • Hi there,

    I’ve been using the WordPress plugin for quite some time, with great results. However, yesterday I started receiving no messages from the web site.

    I tried a test message from the plugin, and this is the error message I get:
    Connection: opening to smtp.sparkpostmail.com:587, timeout=300, options=array ()
    Connection: opened
    SERVER -> CLIENT: 220 2.0.0 smtp.sparkpostmail.com ESMTP ecelerity 4.2.39.65269 r(Core:4.2.39.48) Wed, 25 Jul 2018 16:57:42 +0000
    CLIENT -> SERVER: EHLO https://www.farnellweb.com
    SERVER -> CLIENT: 250-b.mta1vsmtp.cc.aws-usw2b.prd.sparkpost says EHLO to 192.185.4.143:54941250-STARTTLS250-AUTH=LOGIN PLAIN250-AUTH LOGIN PLAIN250-ENHANCEDSTATUSCODES250-PIPELINING250 8BITMIME
    CLIENT -> SERVER: STARTTLS
    SERVER -> CLIENT: 220 2.0.0 continue
    SMTP Error: Could not connect to SMTP host.
    SMTP NOTICE: EOF caught while checking if connected
    Connection: closed
    SMTP Error: Could not connect to SMTP host.

    Can you help me?

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter McFarnell

    (@mcfarnell)

    E-mailed SparkPost, and their response is below. Isn’t this plugin the official SparkPost plugin? Wouldn’t they have updated it to support TLS v 1.1?
    ========
    Thank you for contacting SparkPost Support. We have deprecated TLS v1.0 and you need to use TLS v 1.1 or higher. We have communicated these changes via email to our customers in advance.
    We pushed the TLS changes to go through Monday morning which is likely why you had issues earlier. More information about the TLS deprecation can be found in our blog post here: https://www.sparkpost.com/blog/tls-v1-0-deprecation/

    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 to determine whether it uses TLSv1.1 or higher (traffic will be accepted) or whether it uses TLSv1.0 (traffic will be rejected). These endpoints are described in this support article found here: https://www.sparkpost.com/docs/tech-resources/tlsv1-0-test-hostname/

    There’s probably more to the story. I’m using the SparkPost plugin on a few sites and not getting the error you’re experiencing. I suspect the TLS version is determined by other software on your server–not by the SparkPost plugin. This guidance from SparkPost seems to support that.

    Thread Starter McFarnell

    (@mcfarnell)

    Thank you. I think you are correct, because I have sites on another server that still work fine. I responded to SparkPost, but have not heard back. However, I changed from SMTP to HTTP, and now it works. Any reason I should keep it on SMTP?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘EOF caught while checking if connected’ is closed to new replies.