Webmail URL for clients

Bananenbaas

Hi guys,

We're migrating from cPanel and got a few clients that insists on using webmail.clientdomain.com instead of or next to mail.clientdomain.com. Also a redirect to mail.clientdomain.com is not really accepted. These people don't like the URL changing.

I only see one option in Enhance now, that is to park the webmail.clientdomain.com on the global webmail URL.

Or is it possible to create a CNAME for webmail.clientdomain.com to mail.clientdomain.com? The trouble I run into then is the SSL cert and the serving of the roundcube app. I think it should be possible but maybe a lot of hassle.

Maybe you guys give some advice? And please look at the technical problem and not the clients that's not willing to change. People just don't like change a lot, you should get it.

cPFence

Bananenbaas

You can use mail.clientdomain.com with enhance, and it’s actually recommended in the official documentation. Have a look here:

https://enhance.com/docs/email-role/webmail.html

mendozal

Bananenbaas maybe you can try installing a custom instance of Roundcube for them at that subdomain. Not managed by enhance.

I can’t think of anything preventing that but I might not be seen something.

Bananenbaas

cPFence Thanks, I know I can use that URL but the client insists on using webmail.clientdomain.com as their URL for their roundcube webmail as well. So I'm trying to figure out how and what is the best way of making that possible.

Bananenbaas

mendozal Thanks, will look into that.

nhybgtvfr

you could create a subdomain 'webmail' on the clients main website and configure that to redirect to your global webmail.

that way the clients can continue using webmail.clientdomain.tld, although it will show the global webmail url in the browsers url bar...
and if you're using nginx, it looks like you'd have to manually edit the vhost config to add the redirect, it currently seems to want to put it into .htaccess in the containers folder.. guess that's ok for apache/ols..

Bananenbaas

nhybgtvfr I understand what you mean but then It's easier to park the webmail.clientdomain.com on the webmail.globaldomain.com since this function can be used within Enhance.

What I'm trying to do is get webmail.clientdomain.com working exactly like mail.clientdomain.com.

leighharro

What we do for that is create a webmail.clientdomain.com subdomain in their account with a .htaccess redirect to mail.clientdomain.com.
Ideally I'd love enhance to use or support webmail.clientdomain.com directly but at least the end use can get to where they need to go without any issues.

Bananenbaas

leighharro I would like this as well, for now I've parked the webmail.clientdomain.com on the global webmail URL so it just shows that URL .