Same with -tls1 works OK, without any errors. Here is an output of openssl s_client -connect :443 -ssl3 CONNECTED(00000004)ģ897:error:14094410:SSL routines:SS元_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:1086:SSL alert number 40ģ897:error:1409E0E5:SSL routines:SS元_WRITE_BYTES:ssl handshake failure:s3_pkt.c:530: You can lock it down to relays from specific IPs, and then have it forward to 365.
Stunnel office 365 config windows#
Windows Servers built in SMTP role is pretty limited but gets the job done. OpenSSL version: OpenSSL 0.9.8e-fips-rhel5. We have a few old bastard apps that dont support any sort of modern SMTP config. fixing "fingerprint does not match" errorĬAfile = /path/to/ssl/Īnyone has any insight as to what's happening here? Googled for multiple hours now, can't figure it out. Here is my config: pid = /etc/stunnel/stunnel.pid At the same time, wget reports: OpenSSL: error:14094410:SSL routines:SS元_READ_BYTES:sslv3 alert handshake failure This should always be the first thing to try, if your client application supports the correct settings. Tried using wget, and all is smooth with TLSv1, but error shows up with SSLv3. Option 1: Connect Directly to Office 365 Using the Correct Settings. Connecting from Ubuntu using links - no error. Stunnel configuration file for Office 365 SMTP and POP3 On your application you must set the SMTP server to the IP address of the server/PC running STunnel (must not be the same machine as VMPro, it can be any machine within the network) and you need the use in clear the credentials of the MS Office 365 exchange account. Connecting from CentOS using links - error shows up (tried multiple machines). Not all clients trigger that, for some strange reason. Then I encountered errors in log files: SSL_accept: 1408F10B: error:1408F10B:SSL routines:SS元_GET_RECORD:wrong version number
Everything was smooth, and mostly it works as designed. I'm trying to set up Stunnel to server as SSL cache.
0 kommentar(er)
