Question 1

Why are my RFC6186 SRV records still pointing to the MX host instead of the configured ClientSettingsDomain?

Accepted Answer

A bug caused SRV autoconfig records (_imaps._tcp, _submissions._tcp) to ignore the `ClientSettingsDomain` and fall back to the MX hostname. This has been fixed in commit [3387511](https://www.xmox.nl/b/#3387511f23d8657b6822ab24493e8f7bbb077002). Update to a build that includes this commit, or apply the patch manually. The fix will be part of the next stable release.

Question 2

Why does Mox webmail get stuck on 'loading...' when behind nginx reverse proxy?

Accepted Answer

Mox webmail uses HTTP Server-Sent Events (SSE) for real-time updates, which nginx may buffer by default, causing upstream timeouts. To fix, disable buffering and ensure HTTP/1.1 connection handling in your nginx location block:

```nginx
location / {
    proxy_pass http://localhost:1080;
    proxy_set_header Host $host;
    proxy_set_header Connection '';
    proxy_http_version 1.1;
    proxy_buffering off;
}
```

Alternatively, you can add `proxy_buffering off;` alone as a simpler fix. For more background, see [nginx SSE configuration guide](https://serverfault.com/questions/801628/for-server-sent-events-sse-what-nginx-proxy-configuration-is-appropriate).

Question 3

Why does gobuilds.org return a 400 Bad Request when downloading a Go binary?

Accepted Answer

This error was caused by an expired or outdated Google PGP public key used to verify Go release signatures. The maintainer updated the key in the goreleases repository and the gobuild service. The issue is now fixed. If you still see the error, wait a few minutes and retry the download, or ensure you are using the latest gobuilds URL.

Question 4

Why does the Mox download link show '400 Bad Request' error?

Accepted Answer

The download link at gobuilds.org returns 400 Bad Request due to a cached failed build on the server. The Mox maintainer fixed it by clearing the cache. No user action is required; simply retry the download later or report if the issue persists.

Question 5

How to access Mox admin panel when the server is behind Nginx on a subdomain?

Accepted Answer

Configure Mox to serve AdminHTTP on the internal interface (e.g., localhost:1080). Then set up an Nginx server block for your subdomain (e.g., mail.example.com) that proxies requests to that internal listener. Example Nginx config:

```nginx
server {
    listen 443 ssl;
    server_name mail.example.com;
    ssl_certificate /path/to/fullchain.pem;
    ssl_certificate_key /path/to/privkey.pem;

location / {
        proxy_pass http://127.0.0.1:1080;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host;
    }
}
```

Optionally, add a redirect from root to `/webmail/` with `return 301 https://$server_name/webmail/;`. Restart Nginx and Mox. Now access `https://mail.example.com/admin` for the admin panel. The SSH tunnel is unnecessary in this setup.

mox

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects