Business email on your own domain, without a per-mailbox bill

There is a specific moment when a business starts looking unserious, and it is the moment a quote arrives from yourbusiness2019@gmail.com. Email on your own domain is one of the cheapest credibility upgrades available, and one of the most commonly deferred.

The reason it gets deferred is that the two obvious options both have a catch: per-mailbox subscriptions get expensive as you hire, and self-hosting mail has a reputation for being the hardest thing in system administration. Here is the honest picture of both.

What per-seat email actually costs

Hosted business email runs roughly $5–7 per user per month. That looks trivial for one person and stops looking trivial quickly:

• 1 person: ~$6/month — genuinely fine
• 5 people: ~$30/month — often more than the server hosting your website
• 12 people: ~$72/month — nearly $900 a year for mail

The awkward part is shared addresses. info@, support@, billing@, noreply@ — each one is another seat on most plans, or a workaround with aliases. You end up designing your email addresses around the price list.

Why self-hosting mail has a bad reputation

It is deserved, historically. Running a mail server means operating Postfix for sending, Dovecot for mailbox access, a webmail client, and — the hard part — proving to the rest of the internet that you are not a spammer. That means:

• SPF — a DNS record listing which servers may send mail for your domain
• DKIM — a cryptographic signature on every message, verified against a public key in DNS
• DMARC — a policy telling receivers what to do when SPF or DKIM fails
• Reverse DNS — your server's IP resolving back to your mail hostname
• Reputation — a clean sending IP, which takes time to establish

Get any of these wrong and your mail lands in spam, silently. That failure mode — silent, not loud — is why people are scared of it. You do not find out; your customers just stop replying.

The part that has actually changed

None of that complexity has gone away. What has changed is that it can be generated rather than hand-configured. Every record above is deterministic — it depends on your domain, your server's IP, and a key pair. There is no judgement involved, which means there is no reason a human should be typing it into a DNS panel from a tutorial.

On Simplewala, installing email deploys Postfix, Dovecot, OpenDKIM, and Roundcube webmail as containers, generates your DKIM key pair, and shows you the exact SPF, DKIM, and DMARC records to add at your registrar — filled in with your values, ready to copy. The deeper explanation of how these three records interact is in self-hosted email: DKIM, SPF, and DMARC made simple.

Setting it up

1. Install the mail server on an existing Simplewala server. It runs alongside your website; it does not need its own machine.
2. Add the DNS records shown in the portal — an MX record, plus SPF, DKIM, and DMARC as TXT records.
3. Create your mailboxes. Real accounts, aliases, and catch-alls, as many as you want.
4. Verify delivery by sending a test message to a mailbox at a major provider and checking it arrived in the inbox, not spam.
5. Connect your clients. Roundcube webmail is included; Outlook, Apple Mail, and Thunderbird connect over IMAP and SMTP with TLS.

The whole thing is a dashboard flow. See email hosting for what is included.

Staying out of spam folders

Authentication gets you eligible for the inbox. Reputation gets you there. A few habits that matter more than any configuration setting:

• Warm up gradually. A brand-new IP sending 5,000 messages on day one looks exactly like a compromised host. Ramp up over a couple of weeks.
• Separate transactional from bulk. Password resets and invoices should not share a sending reputation with your newsletter.
• Honour unsubscribes immediately. Spam complaints damage deliverability far more than volume does.
• Start DMARC at p=none. Collect reports for a few weeks, confirm legitimate mail passes, then move to quarantine and eventually reject.
• Keep your list clean. Repeatedly mailing dead addresses is a strong spam signal.

When you should not self-host mail

Being straight about this: if your business runs high-volume marketing campaigns, or email deliverability is existential to your revenue, a dedicated email service provider with a managed reputation team is worth the money. Their entire business is that problem.

Self-hosting is the right call for ordinary business correspondence — sales, support, invoices, contact forms, the day-to-day mail of a small company. That is most businesses, and it is exactly the case where per-seat pricing hurts most.

A reasonable hybrid is common: host your team's mailboxes yourself, and route bulk marketing through a specialist provider. Both can authenticate against the same domain.

What it costs on your own server

Mail runs on a server you are already paying for. There is no per-mailbox charge, so the marginal cost of the fourth, tenth, or thirtieth address is zero. For a growing team that is the entire argument — the number that used to scale with headcount stops scaling.

The wider cost comparison is in what VPS hosting actually costs.

Keep reading

Email hosting Postfix, Dovecot, DKIM, and Roundcube webmail on your own server. DKIM, SPF, and DMARC made simple How the three authentication records actually work together. What VPS hosting actually costs Where per-seat email fits in a real monthly hosting bill. Why port 25 is blocked What an SMTP relay does, and why outbound mail needs one.