Mailcow vs Mail-in-a-Box
Two of the most popular ways to self-host email, with the same Postfix + Dovecot core and opposite philosophies. Mail-in-a-Box is a one-command box for a fresh Ubuntu 22.04 machine that runs on 1 GB of RAM and deliberately has almost nothing to configure. Mailcow is an 18-service Docker groupware stack with a comprehensive admin UI, Rspamd and ClamAV, and a 6 GiB RAM floor. Neither ships a transactional sending API. If that's the gap, we're a third option, covered below.
At a glance
Side-by-side, current as of October 2026 (Mailcow 2026-09a, Mail-in-a-Box v77).
| Mailcow | Mail-in-a-Box | |
|---|---|---|
| Mail stack | Postfix · Dovecot | Postfix · Dovecot |
| Deployment | Docker Compose, 18 services | One setup script, installs onto the OS |
| Supported OS | Any Linux running Docker (full VMs; not LXC/OpenVZ) | Ubuntu 22.04 LTS only, fresh machine |
| Minimum RAM | 6 GiB + 1 GiB swap | 512 MB (1 GB recommended) |
| Antispam / antivirus | Rspamd + ClamAV | SpamAssassin + Postgrey greylisting |
| Webmail | SOGo | Roundcube |
| Calendar / contacts | Yes (SOGo) | Yes (Nextcloud) |
| Exchange ActiveSync | Yes (SOGo) | Yes (Z-Push) |
| DNS | You run DNS elsewhere | Runs its own authoritative DNS (or use external DNS) |
| Backups | Helper script you schedule | Built in, nightly (local, rsync, S3, B2) |
| Customisation | mailcow.conf, per-service overrides, web UI | None by design ("no user-configurable setup options") |
| Admin API | Yes | Yes (control-panel actions) |
| Transactional sending API | No | No |
| Update model | Manual update.sh | Re-run the setup script |
| Automatic rollback | No | No |
| License | GPL-3.0 | CC0 1.0 (public domain) |
| Pricing | Free (paid ServerCow support optional) | Free (donations) |
How they differ
Philosophy: appliance vs platform
Mail-in-a-Box's README states it plainly: there are no user-configurable setup options; it "just works." You give it a fresh Ubuntu 22.04 machine and a hostname, and it configures mail, webmail, calendar, DNS, TLS, backups, a firewall and monitoring for you, making every decision on your behalf. That's the whole point: the fewer knobs, the less there is to get wrong.
Mailcow is a platform you operate. It ships sensible defaults, but everything is adjustable through mailcow.conf, per-service override files and a comprehensive web UI covering domains, mailboxes, DKIM, quarantine, rate limits and SOGo groupware. More to learn, much more you can shape.
Hardware and operating system
This is often the deciding factor. Mail-in-a-Box needs at least 512 MB of RAM (1 GB recommended) and will happily run on the cheapest VPS tier. Mailcow's documented minimum is 6 GiB of RAM plus 1 GiB of swap with the default configuration, rising to 8 GiB for about 5 to 10 users and roughly 16 GiB for a company with 15 ActiveSync phones, because it also runs SOGo, ClamAV, a full-text search engine and MariaDB.
On the OS side, the constraint runs the other way. Mail-in-a-Box's setup script refuses to install on anything except Ubuntu 22.04, so it can't use Ubuntu 24.04 or any other distribution. Mailcow runs wherever Docker does on full virtualisation (KVM, ESX, Hyper-V), on x86_64 or ARM64, but not inside LXC or OpenVZ containers or on a NAS.
DNS
Mail-in-a-Box is unusual in running its own authoritative DNS server. Point your domain's nameservers at the box and it publishes SPF, DKIM, DMARC, DNSSEC, DANE TLSA, MTA-STS and SSHFP records automatically, which removes the most error-prone part of running mail. If you'd rather keep DNS with your registrar, it lists the records to copy across. Mailcow assumes you run DNS elsewhere and shows you the records to create.
Spam filtering
Mailcow ships Rspamd, a modern scoring engine with DKIM signing, DMARC checks and a web interface, plus ClamAV for attachment scanning. Mail-in-a-Box uses the older SpamAssassin together with Postgrey greylisting, and doesn't include an antivirus scanner.
Groupware
Both give you calendar, contacts and phone sync out of the box, through different components. Mailcow's SOGo is one integrated groupware web app: webmail, CalDAV/CardDAV and Exchange ActiveSync together. Mail-in-a-Box assembles the same capabilities from Roundcube webmail, Nextcloud for CalDAV/CardDAV and Z-Push for ActiveSync.
Backups and updates
Mail-in-a-Box takes a nightly backup automatically with Duplicity, to local disk or to remote storage over rsync, S3 or Backblaze B2, with no setup beyond choosing a target. Mailcow ships a backup_and_restore.sh helper script that you run or schedule yourself.
Neither has an automated update safety net. Mail-in-a-Box upgrades by re-running its setup script, which works best on a box nobody has customised. Mailcow upgrades withupdate.sh, which pulls new images and restarts containers. Neither takes a pre-update snapshot, runs a health-check gate or rolls back on failure: if an update breaks something, recovery is manual.
Programmatic sending
Neither ships a transactional sending API. Both expose an admin API for managing users and aliases, but sending from an application means SMTP submission as a real mailbox with its own username and password. There are no domain-scoped API keys, no inbound webhooks and no per-domain analytics in either.
Who each is best for
Choose Mailcow if
- You have 6–8 GiB of RAM to give it and want a full groupware suite.
- You want Rspamd and ClamAV filtering rather than SpamAssassin.
- You need to customise the stack and manage it from one admin UI.
- You need a current OS: Ubuntu 24.04, Debian or ARM64.
Choose Mail-in-a-Box if
- You're running mail for yourself, a family or a small organisation.
- Your budget is a 1 GB VPS.
- You want DNS, TLS and backups handled automatically.
- You'd rather have no settings at all than the wrong ones.
The third option: Vectis Mail
If what's missing from both is a transactional sending API, a modern OS on a mid-size VPS, or an update you don't have to supervise, that's the gap Vectis Mail is built to close. It's self-hosted on the same proven Postfix and Dovecot core, with Rspamd by default, installed by one guided command:
- Runs on Ubuntu 24.04 LTS from 2 GB of RAM without ClamAV (4 GB recommended), so it's lighter than Mailcow and not tied to an older Ubuntu release.
- Domains, mailboxes, aliases and API keys managed from an admin dashboard or the REST API, taking effect immediately with no restarts.
- A 40+ endpoint REST API: transactional sending (single and batch, with attachments), HMAC-signed inbound webhooks, domain-scoped API keys with per-domain rate limits, and analytics.
- Atomic 6-phase updates (snapshot, migrate, pull, deploy, health-check, complete) with automatic rollback, and
vectis verifyto prove the box runs exactly what was published.
To be equally clear about where Vectis Mail doesn't fit: it's Docker-only, and it doesn't yet ship calendar, contacts or ActiveSync; those are on the roadmap, not shipped today. If groupware is a day-one requirement, pair it with a dedicated CalDAV/CardDAV service. See the dedicated Vectis Mail vs Mailcow and Vectis Mail vs Mail-in-a-Box comparisons for the full detail on each.
Frequently asked questions
Is Mailcow or Mail-in-a-Box better?
They're built for different jobs. Mail-in-a-Box is a one-command personal or small-organisation mail server for a fresh Ubuntu 22.04 machine, with almost nothing to configure. Mailcow is a full Docker groupware stack (SOGo, Rspamd, ClamAV) with a comprehensive admin UI and room to customise, at the cost of a much heavier footprint: 6 GiB RAM plus 1 GiB swap minimum. Pick on hardware budget and how much control you want, not on mail quality: both deliver mail through the same Postfix and Dovecot core.
How much RAM do Mailcow and Mail-in-a-Box need?
Mail-in-a-Box needs at least 512 MB and recommends 1 GB; its installer warns below 768 MB. Mailcow's documented minimum is 6 GiB RAM plus 1 GiB swap with the default configuration, with 8 GiB recommended for roughly 5 to 10 users, because it also runs SOGo, ClamAV, a full-text search engine and MariaDB.
Does Mail-in-a-Box run on Ubuntu 24.04?
No. As of Mail-in-a-Box v77 (September 2026), its setup script checks for Ubuntu 22.04 and refuses to install on anything else, including Ubuntu 24.04. Mailcow runs on any Linux host that runs Docker on full virtualisation (KVM, ESX, Hyper-V), on x86_64 or ARM64, but not inside LXC or OpenVZ containers.
Do Mailcow and Mail-in-a-Box both have calendar and contacts?
Yes. Mailcow bundles SOGo, which provides webmail, CalDAV/CardDAV calendar and contacts, and Exchange ActiveSync. Mail-in-a-Box bundles Nextcloud for CalDAV/CardDAV and Z-Push for Exchange ActiveSync, alongside Roundcube webmail.
Does either have a transactional sending API?
No. Both have an administrative API for managing users and aliases, but neither ships a REST API for programmatic sending, inbound webhooks, or per-domain analytics. Sending from an application means SMTP submission as a real mailbox. Vectis Mail is a self-hosted platform built to add that sending API alongside mailbox hosting.
Related comparisons
See how Vectis Mail itself compares to each.
Vectis Mail vs Mailcow →
A transactional sending API and atomic updates with rollback vs Mailcow's web-UI-driven, admin-only surface.
Vectis Mail vs Mail-in-a-Box →
Multi-domain mail with a sending API vs a one-command personal box on Ubuntu 22.04.
iRedMail vs Mailcow →
Another head-to-head: OS-native vs Docker, and OpenLDAP vs none.
Best self-hosted email servers (2026) →
The whole landscape by buyer type, including both of these, compared side by side.