Well, I'm stunned (pun intended): while the output= wasn't accepted (it said it wasn't valid there), changing 127.0.0.1 to localhost seems to have fixed it!

-----Original Message----- From: stunnel-users [mailto:stunnel-users-bounces@stunnel.org] On Behalf Of peter@easthope.ca Sent: Thursday, January 18, 2018 12:20 AM To: stunnel-users@stunnel.org Subject: Re: [stunnel-users] Problems with stunnel and cox.net on Windows 7

From: "Phil Smith III" phs3stuff@cox.net Date: Wed, 17 Jan 2018 21:59:42 -0500

Here's my stunnel.conf, with blank lines and comments removed: client = yes output = C:\temp\stunnel-log.txt taskbar = yes debug = 7 [POP3 Incoming] protocol = pop3 accept = 127.0.0.1:1110 connect = pop.cox.net:995 protocol = smtp accept = 127.0.0.1:25 connect = smtp.cox.net:465

Here it worked for POP3 immediately. Not needed for SMTP. https://en.wikibooks.org/wiki/Oberon/Oberon#Receiving_and_Sending_Email

Before using 1110, check. netstat -tulpn | grep 1110

Correct id, passwd and port are in the MUA?

Separate configurations for POP3 and SMTP. Troubleshoot one at a time. "protocol" shouldn't be necessary. Try this.

[POP3] client = yes output = C:\temp\stunnel-log.txt accept = localhost:1110 connect = pop.cox.net:995

Regards, ... Peter E.