Maybe this is covered elsewhere but cannot find another reference.
If you use mixed server, the user enters an http address, he is redirected to the same via https and then back to http to continue mail session. There is a problem the server is in fact a virtual server and the certificate´s common name does not match.
What I want to accomplish is to avoid certificate common name mismatch by redirecting the user to a fixed https server name independently of his original domain name, i.e.:
http://mail.customer_a.com -> https://mail.customer_a.com (not good because the ssl certificate common name does not match and the user's browser will cry!) -> http://mail.customer_a.com
http://mail.customer_a.com -> https://secure.provider.com -> http://mail.customer_a.com
It would be great if this could be done even without breaking the virtual server functionality, maybe by including a hidden field (or a cookie) in the secure auth form so he can redirected back to the his domain.