Force hhtps on webmail connections

[theone]

Hello folks, I've just change my server to new Data Center, because iWeb NYC go out, I have migrate the all accounts, messages, etc.. but I've must to setting everything from ZERO one time that I don't can use the same IP ADDR on new scope. Well, everything seems to work perfectly, but I want to force my webmail clients fo use https on webmail conections. Acctually I want to foce every "webmail.domin.com" go to "https://mail.domain.com" because I have just one valid SSL certificate on server for core domain. Is it possible ?! Thanks in advance, Kind Brazilian Regards, Luiz.

[L. Mark Stone]

Hello folks, I've just change my server to new Data Center, because iWeb NYC go out, I have migrate the all accounts, messages, etc.. but I've must to setting everything from ZERO one time that I don't can use the same IP ADDR on new scope. Well, everything seems to work perfectly, but I want to force my webmail clients fo use https on webmail conections. Acctually I want to foce every "webmail.domin.com" go to "https://mail.domain.com" because I have just one valid SSL certificate on server for core domain. Is it possible ?! Thanks in advance, Kind Brazilian Regards, Luiz.

Take a look at https://wiki.zimbra.com/wiki/Zimbra_Pro ... mbra_Proxy, but what you most likely want to do is to have zimbraReverseProxyMailMode set to "redirect" on the proxy server, and zimbraMailMode set to "https" on the mailbox servers.

In this way, users who browse to your server's fqdn without https will be redirected to https for login and then their logged in session will stay on https. Having zimbraMailMode means the mailbox service will communicate via https with the proxy.

Separately, you can use virtual hosts too if you like, but it sounds like you'll need a wildcard certificate if you don't have one already.

Alternatively, if your DNS provider offers http redirection records, you can set things up so that a user who browses to webmail.yourdomain.com will get automatically redirected to the Zimbra server now at mail.yourdomain.com.

Hope that helps,
Mark

[theone]

Hello folks, I've just change my server to new Data Center, because iWeb NYC go out, I have migrate the all accounts, messages, etc.. but I've must to setting everything from ZERO one time that I don't can use the same IP ADDR on new scope. Well, everything seems to work perfectly, but I want to force my webmail clients fo use https on webmail conections. Acctually I want to foce every "webmail.domin.com" go to "https://mail.domain.com" because I have just one valid SSL certificate on server for core domain. Is it possible ?! Thanks in advance, Kind Brazilian Regards, Luiz.

Take a look at https://wiki.zimbra.com/wiki/Zimbra_Pro ... mbra_Proxy, but what you most likely want to do is to have zimbraReverseProxyMailMode set to "redirect" on the proxy server, and zimbraMailMode set to "https" on the mailbox servers.

In this way, users who browse to your server's fqdn without https will be redirected to https for login and then their logged in session will stay on https. Having zimbraMailMode means the mailbox service will communicate via https with the proxy.

Separately, you can use virtual hosts too if you like, but it sounds like you'll need a wildcard certificate if you don't have one already.

Alternatively, if your DNS provider offers http redirection records, you can set things up so that a user who browses to webmail.yourdomain.com will get automatically redirected to the Zimbra server now at mail.yourdomain.com.

Hope that helps,
Mark

DUDE ! THANK YOU SO MUCH ! Works perfectly.! THX !!!!

[theone]

Now all requests which comes from by http is going to https (PERFECT)

But, in this server, i have around 6 domains but just a single SSL certificate, is it possible to all requests which comes from webmai.domain1.com go to https://mail.coredomain.com. I really don't remember how it's working on old Server. the fact to http is going to https just works nice for me, but appears certificate issues (for reason that I have 6 domins but just 1 valid SSL). There's some way? If not.. it's already works fine for now.

Thank you

[L. Mark Stone]

DUDE ! THANK YOU SO MUCH ! Works perfectly.! THX !!!!

You are welcome!

As for the multiple domains/single SSL certificate issue, I would recommend the simplest solution would be to add http redirection records in public DNS for each of the additional domains.

Take a look at http://help.dnsmadeeasy.com/managed-dns ... on-record/ for how this works on DNS Made Easy; other DNS providers have comparable services.

Hope that helps,
Mark