I'm trying to use stunnel on a redhat machine to securely check email, via xinetd via pop3d. <br><br>My /etc/xinetd.d/pop3s looks like this:<br>service pop3s<br>{<br> socket_type = stream<br> wait = no<br> user = root<br> server = /usr/sbin/stunnel<br> log_on_success += USERID<br> log_on_failure += USERID<br>
disable = no<br>}<br><br>And netstat just shows xinetd on 995:<br>netstat -apn|grep 995<br>tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2797/xinetd <br><br>When I try to check mail with my client hitting port 995, I get this in /var/log/secure using debug level 7:<br><br>Nov 1 16:17:24 myhostname xinetd[2797]: START: pop3s pid=2840 from=x.x.x.x<br>Nov 1 16:17:54 myhostname stunnel[2840]: stunnel 4.04 on i386-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003<br>Nov 1 16:17:54 myhostname stunnel[2840]: Snagged 64 random bytes from /dev/urandom<br>Nov 1 16:17:54 myhostname
stunnel[2840]: RAND_status claims sufficient entropy for the PRNG<br>Nov 1 16:17:54 myhostname stunnel[2840]: PRNG seeded successfully<br>Nov 1 16:17:54 myhostname stunnel[2840]: Certificate: /usr/share/ssl/certs/stunnel.pem<br>Nov 1 16:17:54 myhostname stunnel[2840]: Key file: /usr/share/ssl/certs/stunnel.pem<br>Nov 1 16:17:54 myhostname stunnel[2840]: FD_SETSIZE=1024, file ulimit=1024 -> 500 clients allowed<br>Nov 1 16:17:54 myhostname stunnel[2840]: FD 4 in non-blocking mode<br>Nov 1 16:17:54 myhostname stunnel[2840]: SO_REUSEADDR option set on accept socket<br>Nov 1 16:17:54 myhostname stunnel[2840]: Error binding pop3s to 0.0.0.0:995<br>Nov 1 16:17:54 myhostname stunnel[2840]: bind: Address already in use (98)<br><br>Any suggestions? <br><br>Thanks!<br><p>
<hr size=1>Want to start your own business? Learn how on <a href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index"> Yahoo! Small Business.</a>