Hi Andy, cool, ASCII art :)
> For now, you'll have to use different conf files, and I'll fix this in the > next release. Thanks a lot for your support. I'm highly pleased by the speed of your answers as well as of Binc IMAP itself. :) Anyway, I already tried another solution: Running a plain Binc IMAP without SSL under sslserver from the ucspi-ssl package. The benefit you'll get from this solution is that you're able to put "recordio" into your run script and get the whole IMAP session logged (which isn't possible with Binc IMAP itself, as far as I see). That way, the command chain is: sslserver (decrypts the connection) -> recordio (records the unencrypted connection) -> bincimapd (handles the big load of IMAP) As far as I can tell, it works fine, with only small caveats: * Binc IMAP still advertises STARTSSL support because it thinks it has an unencrypted connection (which it actually has due to the use of sslserver) * Binc doesn't show the IP address of the connection client in its logs (it shows "???.???.???.???" instead); I think because it tries to read the TCPREMOTEIP environment variable while sslserver sets SSLREMOTEIP instead I'm not yet sure which solution I prefer. Using recordio to debug broken clients sometimes helps a lot, and I don't know if it is better to have SSL included into (as it actually is) or wrapped around (as with sslserver) Binc IMAP from a security/performance/usability/etc point of view. Maybe someone has a comment on that..? :) Jonas
