self hosting email surrender reveals infrastructure gravity
see also: LLMs · Model Behavior
After self-hosting email for decades, a developer shut it down and moved to a provider (source). The post captures how deliverability and abuse controls have become a permanent ops tax. I read it as proof that infrastructure gravity is real.
constraint map
- Spam filtering and reputation systems require continuous upkeep and feedback loops.
- Email deliverability depends on opaque scoring, which small operators cannot influence.
- Reliability expectations have risen while tolerance for downtime has collapsed.
counter-model
Self-hosting still makes sense for sovereignty and compliance. For some teams, owning the stack is worth the operational load. The problem is that the market has moved the goalposts, making deliverability an arms race that most individuals cannot afford.
risk surface
- Centralization increases systemic risk and reduces user choice.
- Outages at large providers now impact a larger percentage of the internet.
- The skills to run email infrastructure decay as fewer people do it.
my take
I treat self-hosting email as an identity statement now, not a default option. That is a loss for the open internet.
linkage
linkage tree
- tags
- #infrastructure
- #ops
- #2022
- related
- [[Self-Hosting Email Ends]]
- [[use one big server]]
- [[cloud credentials cost guardrails]]
ending questions
What would make self-hosting email viable again for a small team?