Running your own mail server: the machine is the small part

Running your own mail server means adopting a profession: the machine is the small part, and the deliverability reputation is the job.

The proposal appears whenever someone totals up what hosted mailboxes cost across the years: run our own mail server on the machine we already pay for, and email becomes free forever. The arithmetic is usually correct and the conclusion is almost always wrong, because the invoice was never the hard part of email. The hard part is that every other machine on the internet is entitled to distrust yours.

Running your own mail server is less like installing software and more like adopting a profession. The machine is the small part: an afternoon of setup, done once. The job is a deliverability reputation, and it is earned receiver by receiver across the internet, kept warm with steady and legitimate volume, and defended from the moment any address sharing your range misbehaves. Your own good behavior is necessary and not sufficient; a neighbor's bad behavior can sink your mail too.

What breaks is rarely the sending; it is the silent non-arrival. A quote goes out and never lands, a password reset evaporates, and nothing on your side reports an error, because rejection is a decision made politely on somebody else's machine. Recovering from that means reading logs, reading rejection reasons, and sometimes writing to blocklist operators you have never met, in their language, on their schedule.

This is the honest case for hosted mail: someone else carries the reputation job full time. They negotiate with receivers at a scale you cannot, they watch the queues at the hours queues misbehave, and their entire business is mail arriving. Paying for that is not a tax on the naive; it is buying out of a second profession you never intended to learn.

The honest case for self-hosting still exists, and it is narrower than the people proposing it usually admit. Real control requirements exist: mail that must never pass through a third party, systems that speak to mail servers directly, environments with rules about where data lives. Those are requirements most businesses hear about and do not actually have, and adopting a profession to satisfy a requirement you do not have is the expensive version of caution.

Before anyone says just set it up, the business should ask three questions and get the answers in writing: who watches the queues, who calls the blocklist operators, and what happens to mail during the outage. We run our own infrastructure and still route most clients' mail to hosted providers, because the control we want for ourselves is not the control their operations need. The technical records themselves belong to the deliverability question and are covered there. Guidance, not guarantees: the machine is the small part, and the reputation is the profession.