Mark Crispin wrote:
You confirmed my suspicion: imapd isn't recognizing that it is being invoked on the SSL port, and therefore is never setting up SSL.
Interesting -- I wonder if TLS really works, then, or is just pretending to. I was assuming it was working, since Thunderbird would present me with my self-signed certificate upon connecting, but perhaps actual encrypted communications never got underway? I'm ignorant on the innards of TLS/SSL, so this is just random musing.
The underlying problem is that tcp_serverport() isn't returning good data.
Am I to assume that the correct values to come back from tcp_serverport() are 143 and 993?
Did you build the software in 64-bit mode? If so, rebuild it in 32-bit mode. There are known issues with 64-bit builds, and this is one of them.
I certainly hope the build is 32-bit since I'm running on a crufty AMD K6 box :-); plus, since I'm using FreeBSD 4.11, I don't believe the gcc-2.95.4 compiler even knows about x86_64. Anyway, I'll look around tcp_serverport() to see what is happening.
Thanks again for your prompt help, --Zem _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
