Mail Server Woes

[Smiler.]

I use a function to send emails from a PLC (ESMTP using AUTH).

I use Telnet to check the settings are ok.

There used to be a line returned after connecting to the server (using port 25) & typing EHLO which stated:

250-AUTH PLAIN LOGIN


I would then enter AUTH LOGIN & away we went.

Note, it returns 503 auth command used when not advertised


The ISP for my websites/mail servers (not BB provider) has advised me:

"This is the expected outcome as port 25 is now a server to server port by design following the migrations.

You'd need to use port 587 and authenticate with credentials in a secure manner.

Over time, we will slowly stop non-SSL ports being used on servers for customer privacy and security but for the moment, some non-SSL ports do work as normal."


Tried using port 587 - same response.

The ISP said "I suspect something isn't being sent but it's not something we have debugged through telnet as it's not a common method of connecting."

I've spent a few hours trying to resolve this & found some comments suggesting that openSSL is a solution:

openssl s_client -starttls smtp -connect smtp.gmail.com:587


I tried this (replacing the relevant parts with my settings) but it would not operate from the CMD prompt.

Further reading suggested downloading binaries at which point my head was ready to implode.

HELP!

[dmsims]

Try putting ssl:// on the FQDN ?

[buggalugs]

If you only need to send emails to one org you might get away with connecting directly to their MX server on 25, that way you won't need to authenticate.

[Prak]

Openssl is a good and valid way to test this kind of thing in a telnet-like way over an encrypted channel - I was using it only today to test secure pop3

It isn't a part of the Windows OS though which is why it isn't available from a command prompt. You will indeed need to download and extract it (the software, aka the .exe, aka the binaries) then in your command prompt, change into the directory you extracted it to.

[colin79666]

Prak said:

Openssl is a good and valid way to test this kind of thing in a telnet-like way over an encrypted channel - I was using it only today to test secure pop3

It isn't a part of the Windows OS though which is why it isn't available from a command prompt. You will indeed need to download and extract it (the software, aka the .exe, aka the binaries) then in your command prompt, change into the directory you extracted it to.

This is where running Windows 10 with the Linux sub system installed (Ubuntu) comes in handy

[Prak]

colin79666 said:

Prak said:

Openssl is a good and valid way to test this kind of thing in a telnet-like way over an encrypted channel - I was using it only today to test secure pop3

It isn't a part of the Windows OS though which is why it isn't available from a command prompt. You will indeed need to download and extract it (the software, aka the .exe, aka the binaries) then in your command prompt, change into the directory you extracted it to.

This is where running Windows 10 with the Linux sub system installed (Ubuntu) comes in handy

Well except you might as well give up on encryption with all that slurping going on!