webmail.domain.ext mirror domain.ext/roundcube

Sorry for the potentially odd title.

In short, what I would like to accomplish is that anyone visiting webmail.domain.com would see the content of domain.ext/roundcube (while remaining on the webmail.domain.ext URL). Is there any potential way of doing this?

We currently use this on our existing site. Just curious as to how I can pull this off using Interworx.

Please let me know if there are any details I might have left out that would help figuring this out.

1 Like

Hi scubes13

I hope you don’t mind, but I do not think there is an easy way to do this, although I have not tried myself.

I am thinking if you setup a subdomain and then manually change the dir from the vhost for siteworx, that might work, but then when accessing the webmail, it may defer back.

Ofcourse, other users may have a solution, so please be patient.

I hope you don’t mind but I also do not understand why you would want to, sorry. I think it’s a question in what’s in a name, so to me I cannot see the difference between webmail,example.url or example.url/webmail, but that’s just me sorry.

I hope you don’t mind my thoughts

Many thanks


I believe the main reason behind this request and many like it is to assist with minimal disruption to hosted clients when migrating from cpanel to interworx

i believe a great feature to add to interworx would be to provide this as an option in the settings for multi webmail client interface.to change the main login option page location to webmail.domain.com

Im updating this post 7 years on and there is still no simple solution

i believe the correct way to do this is they way cpanel does which is to use mod proxy
i don’t believe editing the vhost file of clients is the ideal way to fix this and often ends up breaking when attempting to login to the client

This could be possible using templates upon account creation to create a subdomain " webmail.domain.com" and installing your webmail client of choice or page similar to the current default in interworx 7. i believe this would be the most stable way to do this as after the client reaches the login page it would be of no consequence to the client if the address reflects domain.com/webmail after login


Many thanks and I still do not see the difference that users have to access webmail sorry. I do understand the wording differences though, just not the users who insist on their original domain access to it!

However, there are many changes that you could make, eg we set nodeworx, siteworx, webmail, horde, roundcube etc… to redirect to our FQDNserver for accessing those UI. so all a user has to do is goto their domain and type theirdomain.url/siteworx or webmail etc… and it takes them to the correct login (siteworx login also fills in the domain name required for access, so all the user has to do is complete their username and password).

WHMCS is different, and users can login to whmcs account and access siteworx without logging in

If Cpanel import creates the subdomain, then all you need to do is add the following lines to iworx.conf and it should redirect the subdomain. Please remember to change http://mainFQDNforwebmail.url to your correct url and we use http so it does not trigger https warning, as we have a http to https rewrite on http for FQDNserverurl

I hope that helps a little but sorry if I am wrong

Many thanks


RewriteEngine On
RewriteCond %{HTTP_HOST} ^webmail..$ [NC]
RewriteRule ^(.*) http://mainFQDNforwebmail.url/$1 [L,R]

Just to leave a note on this, we do have an open feature request to look into the possibility of doing this. The exodus from cPanel to us has caused a shift in priorities partially due to the desire to make onboarding for those leaving cPanel a little easier. Having said that, there is a LONG list of these features that need to be worked on to bring this stuff in line so it’s safe to assume they won’t all appear tomorrow. Just know that your requests are being heard.

1 Like