So I have a queue of 3 emails to send, via MS outlook smtp.
All 3 will send fine.
At a later time, 2 will send and I get this in server output:
Email was not sent due to exception javax.mail.MessagingException Could not convert socket to TLS
Sure enough, that 3rd email was not sent. It is not in the outlook Sent or draft folder. I think its still on the server unsent by Aware. But why?
... but eventually it will go out.
From the server output tab: The next time aware did this: "Sending unsent email..."
my email (after throwing the obligatory 'Incorrect header check' warning) was sent.
Do we know Aware is using TLSv1.2 now?
Stack overflow thread here.
Email Error: Could not convert socket to TLS
Email Error: Could not convert socket to TLS
Click Here to see a collection of my tips & hacks on this forum. Or search for "JaymerTip" in the search bar at the top.
Jaymer
Aware Programming & Consulting - Tampa FL
Jaymer
Aware Programming & Consulting - Tampa FL
Re: Email Error: Could not convert socket to TLS
Getting the same problem here for 3 different customers and the problem all occurred at the same time around 4 to 6 weeks ago.
I've set up an unsent Email BO to monitor it from the app and set up a process to resend the email manually.
Resending can also fail multiple times.
I've noticed this only happens with outlook email addresses as well.
I've set up an unsent Email BO to monitor it from the app and set up a process to resend the email manually.
Resending can also fail multiple times.
I've noticed this only happens with outlook email addresses as well.
Re: Email Error: Could not convert socket to TLS
Hey all,
We had the same problem a few weeks ago and 90% of the email failed especially to recipients on O365. I suspect they only accept secure connections or something. After allot of research we discovered we had to upgrade the java mail component in AIM. we downloaded version 1.6.2 and replaced the AIM version. After this we did not see the error again.(its been a few days now). See link below.
@support, maybe this can be added / upgraded in the next release.
https://maven.java.net/content/reposito ... -1.6.2.jar
We had the same problem a few weeks ago and 90% of the email failed especially to recipients on O365. I suspect they only accept secure connections or something. After allot of research we discovered we had to upgrade the java mail component in AIM. we downloaded version 1.6.2 and replaced the AIM version. After this we did not see the error again.(its been a few days now). See link below.
@support, maybe this can be added / upgraded in the next release.
https://maven.java.net/content/reposito ... -1.6.2.jar
Last edited by karelh on Fri Oct 29, 2021 10:48 am, edited 1 time in total.
Re: Email Error: Could not convert socket to TLS
Just tried your solution Karelh and the email sending is working now.
Thanks for your help.
I will also second the request to have this added in the next AIM release.
Thanks for your help.
I will also second the request to have this added in the next AIM release.
-
- Posts: 7526
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: Email Error: Could not convert socket to TLS
The new build 2944 supplies the newest mail.jar
Aware IM Support Team
Re: Email Error: Could not convert socket to TLS
Thanks to all for the replies.
Downloaded that file, renamed it to "mail.jar" and replaced the 4 instances of it that I found - unsure which one REALLY was the needed one.
Restarted aware, queued my emails and BAM BAM BAM - what had stuttered for up to several hours went out right away.
Sweeeeeet!
Downloaded that file, renamed it to "mail.jar" and replaced the 4 instances of it that I found - unsure which one REALLY was the needed one.
Restarted aware, queued my emails and BAM BAM BAM - what had stuttered for up to several hours went out right away.
Sweeeeeet!
Click Here to see a collection of my tips & hacks on this forum. Or search for "JaymerTip" in the search bar at the top.
Jaymer
Aware Programming & Consulting - Tampa FL
Jaymer
Aware Programming & Consulting - Tampa FL