Hello list, there has been some discussion on the qmail-ldap connection-forwarding feature for clusters when using ssl with the tcpserver patch. Unfortunately I have not seen a definitive reply on whether or not it supposed to work with the latest qmail-ldap patch.
My setup: user --pops-on-port-995--> frontend_server_with_auth_pop --pop-on-port-110--> mailbox_machine Connection forwarding works fine for non-ssl connections. Connection forwarding does not work with ssl-connections, the connection gets closed right after sending the "PASS XYZ" line (the connection forwarding code in auth_mod.c kicks in at that time). I can see in tcpdump that the frontend server is connecting to the mailbox_machine port 110 just fine, sends username and password and gets the "+OK" reply. Right after this the connection of the user to the frontend_server closes. Is this a bug or is this (currently) expected behaviour? IMHO the tcpserver instance on the frontend_server should do the ssl en- and decryption to the user for the connection forwarding auth_pop just fine!? best regards, Jochen
