Installing¶
There are two ways in, and they are different jobs.
-
Nothing to preserve. One command brings up the server, the console, the webmail and a proxy for HTTPS, and hands you a working domain, a first mailbox and the DNS records to publish.
-
You already run one. The store is copied rather than converted, so accounts, passwords, sessions, certificates, tenants and mail all arrive intact, and the old install stays standing for a rollback.
What you need either way¶
- A Linux machine with Docker, and a provider that lets it send on port 25. Many cheap hosts block it; check before you start.
- A domain, and access to its DNS.
- Ports 25, 465, 993 and 443 reachable. Add 995 and 4190 if you want POP3 and ManageSieve — see Protocols, because you may not.
You do not need an account with anyone, and nothing phones home.
What gets installed¶
Four containers on a private network, with only the proxy publishing ports:
| Service | What it does | Where it listens |
|---|---|---|
| INBUXA Server | Carries the mail | 25, 465, 993, 995, 4190, and its API behind the proxy |
| INBUXA Admin | The console | 443, through the proxy |
| INBUXA Webmail | Where people read mail | 443, through the proxy |
| Caddy | TLS, and the front door | 80, 443 |
The console and the webmail are separate programs that talk to the server over JMAP. They do not have to live on this machine, and there are good reasons not to put them here — see Where each service goes.
No web interface on the mail host
The server installs no web interface of its own and downloads none at
first boot. /admin and /account answer 404. Administration is INBUXA
Admin's job, and it is deployed separately. Why.