Greetings!
I'm attempting to do some strange things for stranger reasons, so of
course the problems I'm running into are my fault.
That said...
I'm trying to run an IMAPD with SSL on two ports on a system. One on
port 993 and one on port 994. This I've done by compiling a regular
imapd (gcc Solaris) as /usr/sbin/imapd, and a second copy of the binary
with changed port definitions as /usr/sbin/imapd2
However, the imapd software doesn't seem to recognize that a system
connecting to it on port 994 is trying to talk SSL with it.
I looked through the source and found the c-client code hard coding port
993 to the SSL port, so I thought perhaps imap4v1 compiles the c-client
definitions in somehow, and changed them in c-client, then recompiled.
No dice, though. When I connect on port 994 with a client attempting to
talk SSL, I get a nice long hang.
Does anyone have any quick clarifications for me as to how the
IMAPSSLPORT definition in imap4r1.c ends up in the 'imapd' binary? If at
all?
More importantly, am I going about this the right way at all?
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
