Description
Currently mox's behavior is to listen for all subdomains for /admin/, / (Account page) and /webmail/ (If enabled) web path.
This caused issues when using Web forwarding function. For example, I want to use Roundcube Mail as Webmail client, I setup a docker image and use mox as reverse proxy to serve it.
First, I host the Webmail at webmail.example.com, but any access just results in 404 not found, and when I checked the log, all request is redirected to account panel because the default path is mapped to /. So, I map the account panel path to /account/, this resolved the problem.
But there's still issues. On the subdomain webmail.example.com or default mail domain mail.example.com or just any other subdomains, accessing path like /admin/ will always be redirected to mox's page, not the one belongs to that application. For Roundcube, there's no /admin/ page so it's just fine though.
In my case, I just give up using that server for hosting anything else but the mail server, and cancelled any other subdomain, and map my Roundcube Webmail to mail.example.com, as a root path. This perfectly solved any potential issues.
I suggest only to listen for path like /admin/ within the main mail domain, so the web forwarding won't conflict with other web applications. This will greatly improve mox's usability.
Also, it seems that proxy pass is not fully supported by mox, so PHP FastCGI and some common tools are unable to work. Though this is not the point of this issue, I add it here.