• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    javax.mail.MessagingException: Could not convert socket to TLS

    Mango feedback
    2
    3
    2.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MattFoxM
      MattFox
      last edited by

      Using mango 3.7.7, cannot send emails via our gmail account.
      I've configured an application password and yet I receive this error:

      {"cause":"MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: Could not convert socket to TLS;\n  nested exception is:\n\tjavax.net.ssl.SSLHandshakeException: Invalid CertificateVerify signature. Failed messages: javax.mail.MessagingException: Could not convert socket to TLS;\n  nested exception is:\n\tjavax.net.ssl.SSLHandshakeException: Invalid CertificateVerify signature","smtpSessionLog":"DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Oracle]\nDEBUG SMTP: useEhlo true, useAuth true\nDEBUG SMTP: trying to connect to host \"smtp.gmail.com\", port 587, isSSL false\n220 smtp.gmail.com ESMTP x10sm15856991pff.214 - gsmtp\nDEBUG SMTP: connected to host \"smtp.gmail.com\", port: 587\nEHLO mangoGT5191\n250-smtp.gmail.com at your service, [122.56.205.5]\n250-SIZE 35882577\n250-8BITMIME\n250-STARTTLS\n250-ENHANCEDSTATUSCODES\n250-PIPELINING\n250-CHUNKING\n250 SMTPUTF8\nDEBUG SMTP: Found extension \"SIZE\", arg \"35882577\"\nDEBUG SMTP: Found extension \"8BITMIME\", arg \"\"\nDEBUG SMTP: Found extension \"STARTTLS\", arg \"\"\nDEBUG SMTP: Found extension \"ENHANCEDSTATUSCODES\", arg \"\"\nDEBUG SMTP: Found extension \"PIPELINING\", arg \"\"\nDEBUG SMTP: Found extension \"CHUNKING\", arg \"\"\nDEBUG SMTP: Found extension \"SMTPUTF8\", arg \"\"\nSTARTTLS\n220 2.0.0 Ready to start TLS\n","mangoStatusCode":5000,"mangoStatusName":"GENERIC_500","localizedMessage":"Email send failure"}
      

      Any ideas on what to do to fix this?

      Fox

      Do not follow where the path may lead; go instead where there is no path.
      And leave a trail - Muriel Strode

      1 Reply Last reply Reply Quote 0
      • danD
        dan
        last edited by

        Hey mate, can the underlying host machine connect to the mail server on that port?

        Even try just...

        telnet smtp.gmail.com 587
        

        See if you get an answer similar to...

        220 smtp.gmail.com ESMTP p9sm17466733pfq.136 - gsmtp  
        

        Although it does mention TLS so 587 should be correct? Certificate error is weird.

        1 Reply Last reply Reply Quote 0
        • MattFoxM
          MattFox
          last edited by MattFox

          Ah good idea man,

          mondays...

          EDIT:

          220 smtp.gmail.com ESMTP x15sm16801291pfa.80 - gsmtp
          

          I get the feeling this is JDK related...

          Do not follow where the path may lead; go instead where there is no path.
          And leave a trail - Muriel Strode

          1 Reply Last reply Reply Quote 0
          • First post
            Last post