I'm trying to use stunnel on a redhat machine to securely check email, via xinetd via pop3d.
My /etc/xinetd.d/pop3s looks like this:
service pop3s
{
socket_type = stream
wait = no
user = root
server = /usr/sbin/stunnel
log_on_success += USERID
log_on_failure += USERID
disable = no
}
And netstat just shows xinetd on 995:
netstat -apn|grep 995
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2797/xinetd
When I try to check mail with my client hitting port 995, I get this in /var/log/secure using debug level 7:
Nov 1 16:17:24 myhostname xinetd[2797]: START: pop3s pid=2840 from=x.x.x.x
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
Nov 1 16:17:54 myhostname stunnel[2840]: Snagged 64 random bytes from /dev/urandom
Nov 1 16:17:54 myhostname
stunnel[2840]: RAND_status claims sufficient entropy for the PRNG
Nov 1 16:17:54 myhostname stunnel[2840]: PRNG seeded successfully
Nov 1 16:17:54 myhostname stunnel[2840]: Certificate: /usr/share/ssl/certs/stunnel.pem
Nov 1 16:17:54 myhostname stunnel[2840]: Key file: /usr/share/ssl/certs/stunnel.pem
Nov 1 16:17:54 myhostname stunnel[2840]: FD_SETSIZE=1024, file ulimit=1024 -> 500 clients allowed
Nov 1 16:17:54 myhostname stunnel[2840]: FD 4 in non-blocking mode
Nov 1 16:17:54 myhostname stunnel[2840]: SO_REUSEADDR option set on accept socket
Nov 1 16:17:54 myhostname stunnel[2840]: Error binding pop3s to 0.0.0.0:995
Nov 1 16:17:54 myhostname stunnel[2840]: bind: Address already in use (98)
Any suggestions?
Thanks!