Luke Deller wrote:

Hi Tom,

...

OK, this has been nothing but a bust.

I've just read this thread, and it looks to me that you have stunnel configured incorrectly for use with inetd.

Did you see this documentation? http://www.stunnel.org/faq/stunnel.html#inetd_mode

...

the error keeps saying that port 993 is already in use.

This is because you have configured stunnel to bind to port 993 using an "accept" option in the configuration file. When using stunnel with inetd, stunnel should not bind to any port; it is inetd which binds to a port. When a client connects to inetd, then inetd will launch stunnel with stunnel's stdin and stdout streams hooked up to the connected socket.

Made some progress.

Got past the SSL version. Fixed my firewall to permit IMAPS sessions.

confirmed my firewall settings by changing to IMAP and running directly against the imap server.

Changed firewall settings from imap to imaps.

Keep timing out. Same problem for Mac Mail application (which isn't great) and Debian's Icedove. This is as far as I can get.

2007.11.05 05:43:56 LOG7[27692:47518144360528]: Connection from 65.29.101.30:49841 permitted by libwrap 2007.11.05 05:43:56 LOG5[27692:47518144360528]: inetd connected from 65.29.101.30:49841 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): before/accept initialization 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 read client hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write certificate A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server done A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 flush data