[stunnel-users] Problems with stunnel and cox.net on Windows 7

Phil Smith III phs3stuff at cox.net
Thu Jan 18 17:21:28 CET 2018


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 at stunnel.org] On Behalf Of peter at easthope.ca
Sent: Thursday, January 18, 2018 9:51 AM
To: stunnel-users at stunnel.org
Subject: Re: [stunnel-users] Problems with stunnel and cox.net on Windows 7

P.s. 

From:	"Phil Smith III" <phs3stuff at 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.

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

_______________________________________________
stunnel-users mailing list
stunnel-users at stunnel.org
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users



More information about the stunnel-users mailing list