Could not convert socket to TLS

Namkul

Member
Joined
Jul 6, 2019
Posts
8
Likes
4
Hi,
Ever since the new update from version 6 BETA 2 to Beta 3. I could not receive email alert , it returned an error " Could not convert socket to TLS". It was working great before then.No changes were made in the email configuration.

Thanks

Lukman
 
Hi,

There were no changes to the mail functionality in our latest release. Did you make any changes to your settings? Who are you connecting to for email?
If you made changes to email settings, then it's best to restart MotiveWave after clicking the Apply button. This will ensure that the new settings take effect.
 
Dear support,

I'm getting the following error message when i try to send a test email:

" Could not convert socket to TLS".

I'm trying to setup the SMTP settings for outgoing email to get alerts for e.g.

I've tried all protocols (Text / TLS / SSL) but none work.

The email i am using is from Protonmail and i have installed the Proton Mail Bridge that enables SMTP. All seems active and working connection wise.

Thanks in advance for your support.

Marius
 
Hello @gaiusMarius and welcome to the MW-forums :)

I did an online search and this seems to be the way to go:
https://clean.email/blog/email-settings/protonmail-email-settings

so you would set:
  • 127.0.0.1 as SMTP server (the bridge runs a client on your PC, so localhost would be used as servername)
  • 1025 as port
  • TLS as protocol
  • your full proton-email-address as username
  • and apparently no password (since Bridge generates one)
  • (I believe you can chose whatever you want as 'from' email, since the emailheader will be generated by Bridge accordingly, but it would probably be safe to enter your full proton-email-address there as well ?)
Does that work ?
 
Hi Spin, thanks for the warm welcome and support!

However i've followed the steps described but still am facing the same issue. All described in the link shared and on your post has been followed.

Any other suggestion? :/

Thanks in adv!
 
And you are 100% sure the Proton-bridge was running at the time ?

And was it listening on port 1025 ? (test with "telnet localhost 1025" in a commandprompt / cmd)
 
yep, its running on boot now. I've tried restarting MotiveWave several times also.

When i enter "telnet localhost 1025" in terminal i get the following:
"
telnet localhost 1025
Trying 127.0.0.1...
Connected to localhost.
"

seems to be working but still get error message when click "Send Test Email"...
 
ok, thanks for checking.

So this tells us the Protonmail-bridge IS running and DOES accept connections on port 1025.

No idea what else could be wrong here, I am afraid ?

Did you try configuring MW to send mail over another provider's SMTP-server ? (gmail, hotmail, yahoo, ...)
 
Top