Right, I had done that:
Yes, I have protocol = pop3 and protocol = smtp; I’ve tried commenting them out individually, no change that I can see.
The doc really isn't clear about why you'd want/need these, by the way.
But your earlier suggestion (localhost instead of 127.0.0.1) seems to have worked. Still a mystery. I'll be tinkering on machine2 tonight, and then will try on the wife's machine!
-----Original Message----- From: stunnel-users [mailto:stunnel-users-bounces@stunnel.org] On Behalf Of peter@easthope.ca Sent: Thursday, January 18, 2018 9:51 AM To: stunnel-users@stunnel.org Subject: Re: [stunnel-users] Problems with stunnel and cox.net on Windows 7
P.s.
From: "Phil Smith III" phs3stuff@cox.net Date: Wed, 17 Jan 2018 21:59:42 -0500
protocol = pop3
The stunnel(8) manual has this. "protocol = PROTO application protocol to negotiate TLS This option enables initial, protocol-specific negotiation of the TLS encryption."
Is there any need for protocol-specific negotiation? Why? Stunnel provides a tunnel and POP3 works inside. That's all. Try the configuration without the protocol option.
Regards, ... Peter E.