I agree with This too. Commenting the Comcast stanzas should fix the issue. However, as explained by the user, the config file was working with an older stunnel version (circa 2013). Perhaps that version did not check the error condition...
Regards Jose > El 19/10/2016, a las 1:21 p.m., [email protected] escribió: > > John H Hoffmann wrote: > >> upgraded to latest sTunnel v 5.36. > >> In restarting sTunnel I immediately got a >> 'server down' error > >> [ ] Service [pop3s] (FD=432) bound to 0.0.0.0:995 > >> >> [!] bind: Permission denied (WSAEACCES) (10013) >> >> [!] Error binding service [comcast-pop3] to 127.0.0.1:995 > > > You probably have in the stunnel.conf something similar to: > > [pop3s] > accept=995 > {...} > > [comcast-pop3] > accept=127.0.0.1:995 > {...} > > accept=995 == 0.0.0.0:995 == (all localhost IPv4 addresses):995 > > Which includes 127.0.0.1:995 > > When the [comcast-pop3] service tries to bind to port 995 > it fails because it is already bound at the [pop3s] service. > > Gishpuppy | To change the delivery settings for this email, click here: > http://www.gishpuppy.com/cgi-bin/[email protected] > _______________________________________________ > stunnel-users mailing list > [email protected] > https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users _______________________________________________ stunnel-users mailing list [email protected] https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
