The problem
The company relied on a third-party email provider with opaque data handling, rising per-user charges and rigid limits on mailboxes and storage.
- Concern over who could access email content
- Per-user licence and storage costs that rose with headcount
- Little control over spam rules and mailbox policies
What we built
A dedicated AWS environment owned by the client, running the open-source Mailcow platform for SMTP, IMAP, spam filtering and DKIM/DMARC, with quotas, limits and backup policy set by the company rather than a vendor.
- A client-owned AWS account, so the infrastructure is theirs outright
- Mailcow with integrated spam and security controls
- Custom mailbox quotas, user limits and spam rules
- A backup strategy for mail data and configuration
Outcome
The company controls where its mail lives, who can read it and what it costs. Adding a mailbox is a setting, not a purchase.
Tested by a real outage
On 12 and 13 November 2026, Microsoft's Exchange Online was unavailable worldwide for about 24 hours, which in Malaysia covered a full working Friday. Mail on the self-hosted platform does not pass through that service, so it was sent and received as usual and business carried on. A separate system is not immune to failure. It simply does not fail at the same time as everyone else's.
- AWS
- Mailcow
- Docker
- DKIM / DMARC / SPF
- Automated backups