But for how long, we don't know - Heart Internet has never been a good communicator in the past and has often made changes without notifying customers, hence the lack of confidence here.
#Stunnel timeoutclose software#
cert = C:\Program Files\stunnel\config\stunnel.pemĪs can be seen from the log below, it offers STARTTLS as the ISP indicates, but it doesn't require us to use it, since we can still send plain text e-mails with other software to this port. It works in as far as mail is delivered successfully (from our non-encrypting client software, through stunnel), and the stunnel log appears to indicate that it is using TLS, but given that it has not been necessary for me to explicitly say within the stunnel configuration that I wish to use STARTTLS, this does not achieve the test I want, which is to prove conclusively that it will not use plain text at all.
The certificate file stunnel.pem is the file supplied with stunnel. I have therefore configured stunnel with the intention of using encryption - configuration below. They have implied that port 587/STARTTLS will soon be required. We have been sending SMTP mail to our domain host Heart Internet in UK via port 587 in plain text for some time but the ISP has indicated it intends to drop 'legacy authentication', whatever that means exactly. I need a way to check that my configuration of stunnel is encrypting SMTP mail as intended and not just sending plain text.
0 kommentar(er)
