Nigh 2007-10-13 20:30 -0400, Tom Allison spoke:
netstat -ltp shows inetd is listening to port 993.
$ grep imaps /etc/inetd.conf If you already have inetd listening on that port, perhaps you already have a functioning IMAPS server, and don't need stunnel at all. What do you get when you $ openssl s_client -connect localhost:993 If it looks like imap with lots of SSL handshake first, then you've already got IMAPS. Pat yourself on the back and call it a day . Else, you can remove the entry from /etc/inetd.conf and HUP inetd, and then your stunnel should be able to bind port 993. It is also possible you don't have the imap server listening on port 143 (cleartext) at all. Again, 'grep imap /etc/inetd.conf' to see what it has. You can use exec in stunnel if you don't already have imap listening on 143. -- Brian Hatch "What are we going to do? Systems and What are we doing? What are we doing! Security Engineer Hello! I am waiting for an answer!" http://www.ifokr.org/bri/ --Reegen Every message PGP signed