The setup guide walks you through getting your own box set up. See our discussion forum for tips about that. This is a challenge faced by everyone who runs their own mail server, with or without Mail-in-a-Box. Other mail services might block or spam-filter email sent from your Mail-in-a-Box.

Note that while we want everything to “just work,” we can’t control the rest of the Internet. Control panel functionality can also be accessed over the RESTful HTTP API ( API documentation). The control panel displays comprehensive status checks for DNS records and system activity/monitoring and supports TOTP-based two-factor authentication for login. Mail-in-a-Box includes a web-based control panel where you can add mail accounts, mail aliases, and custom DNS records and set up backups. It also supports simple static website hosting (since the box is serving HTTP anyway), or you can host a website elsewhere (just add custom DNS records in your Mail-in-a-Box's control panel). Your box can host mail for multiple users and multiple domain names. TLS certificates are automatically provisioned from Let’s Encrypt. When enabled, DNSSEC (with DANE TLSA) provides a higher level of protection against active attacks with other mail servers also running DANE TLSA.

The box also includes automatic DNS configuration when you let it become your nameserver so that it can set important DNS records for mail deliverability and security including SPF, DKIM, DMARC, and MTA-STS. The box also includes other standard mail functionality like spam protection (spam filtering and greylisting), mail filter rules, email client autoconfiguration, and automated backups to Amazon S3 and other services.

Nextcloud email