Thanks to Corinna's help and others, I actually added the following 2
lines to the services file (found either using cygwin at /etc/services
or c:\windows\system32\drives\etc\services):
imaps 993/tcpimaps #Secure Internet
Message Access Protocol
pop3s
On the advice of another post I also tried the following to verify what
was being broadcast on port 993 and received the following:
$ openssl s_client -connect localhost:993
CONNECTED(0003)
3564:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:188
:
--
Unsubscribe info:
Briefly Im trying to use cygwin's uw-imapd port to attempt to establish
an imap connection over port 995 and 993. I have successfully run the
daemon over the non-secure port.
Ive created the necessary .key and .pem files and placed them in
etc/ssl/certs. First of all Im not sure if this is the
On Mar 8 10:44, Kevin Hilton wrote:
Briefly Im trying to use cygwin's uw-imapd port to attempt to establish
an imap connection over port 995 and 993. I have successfully run the
daemon over the non-secure port.
Ive created the necessary .key and .pem files and placed them in
Kevin Hilton wrote:
Briefly Im trying to use cygwin's uw-imapd port to attempt to establish
an imap connection over port 995 and 993. I have successfully run the
daemon over the non-secure port.
Ive created the necessary .key and .pem files and placed them in
etc/ssl/certs. First of all
René Berber wrote:
[snip]
inetd is an on-demand server, so it's not strange that nothing is listening to
ports 993 and 995, what is strange is that something is listening to ports 110
and 143.
Wrong statement, sorry, of course inetd should be listening.
--
René Berber
--
Unsubscribe info:
6 matches
Mail list logo