系统与基础设施cfenollosa.com
自托管邮件 23 年后，我认输了
After self-hosting my email for twenty-three years I have thrown in the towel
2022 — 2023，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
作者自托管电子邮件 23 年后最终放弃，转用商业邮件服务商。文章讲述了大厂（Gmail、Outlook 等）凭借 IP 信誉和严格的收信策略，让独立邮件服务器越来越难正常收发信件，形成寡头垄断。
为什么经久不衰：它记录了开放互联网被少数巨头逐步收编的过程，是关于自托管可行性与网络去中心化的长期讨论的代表之作。
HN 评论精选
自托管依然可行，但必须严格做好各项配置，并选择 IP 信誉好的托管商。
我自托管邮件 12 年了。偶尔会被屏蔽，通常是 Outlook，有一次是 Yahoo。我加入了他们的发件人计划，但他们根本不联系 postmaster@，不过发几封邮件通常 24 小时内就能解封。同意楼上说的：很多大服务商自己都不好好执行他们强求别人做的 SPF/DKIM/DMARC。如果我们不坚持运营自己邮件服务器的自由，这种自由就会因无人行动而被夺走。关键是把该做的做好：DMARC、DKIM、SPF、服务器维护、好的密码策略，以及 IP 信誉——最好选不允许 VPN 端点的 VPS 提供商，这样分到的 IP 信誉更可靠。
zahllos查看英文原文
I'm on 12 years of self hosting email and counting. Once every so often, I do end up being blocked, usually by Outlook and once by Yahoo. I'm in their 'sender program' and they still don't actually bother to contact postmaster@, but a few emails is usually enough to unblock the block within 24h. Agree with a sibling comment that many major providers fail to operate the SPF/DKIM/DMARC tools they insist you do. Each to their own, but ultimately if we don't hold on to the freedom to operate our own mailservers, it will be taken away through inaction. This means doing some things right: DMARC, DKIM, SPF of course, server maintenance, good password policies and of course IP reputation. The best way I can recommend for IP reputation is to use a dedicated provider or VPS provider that disallows things like VPN endpoints, where it is less likely they'll assign an address with a poor reputation. A good provider might also ask you what you intend to host, and you might be able to discuss IP addresses with them.
问题根源是巨头缺乏维护开放邮件生态的动力，自托管是值得捍卫的自由。
我自托管邮件 20 多年了，问题不大，可能是我运气好。看这里的评论让我非常难过。所有让我用服务商的回答都没抓住重点：互联网被创造出来就是为了有众多独立节点，而不是让每个人都依赖几家被认可的提供商。我应该能运行自己的邮件。真正的问题是缺乏激励——大公司不在乎邮件，它不赚钱、难以控制，无法变成围墙花园锁定用户，所以只得到最少的关注和防御性措施。要么解决垃圾邮件问题，要么情况会更糟，而大公司不会替我们解决。
jwr查看英文原文
I've been hosting my mail for 20+ years now, with minor issues. I guess I've been lucky. Reading the comments here makes me incredibly sad. Every answer that tells me to use a provider misses the point. The Internet was created so that there could be many independent nodes, not so that everybody has to rely on one of several blessed providers. I should be able to run my own E-mail. The real problem is lack of incentives. The big corps do not care about e-mail. It doesn't make money and isn't easily controllable. You can't turn it into a walled garden and lock users in. So, it gets minimal attention, and only defensive measures are developed. Either we solve the spam problem, or things will get worse. The big tech corps won't solve it for us.
建议成立自托管者联盟，集体争取小服务器的平等对待。
也许需要一个自托管者可以加入的协会/联盟？它可以倡导遵守开放标准、为小型服务器争取平等地位，也可以作为小服务器管理配置最佳实践的资料库。是否可以挂在 FreedomBox 这类现有组织之下？
femto查看英文原文
Maybe there needs to be a self-hosting association/union that self-hosters can join? It could advocate for adherence to open standards, and an equal standing for small servers. It could also be a repository of advice for current best practise in small server administration and configuration. Should it be under the auspices of an existing group such as FreedomBox?
折中方案：掌控域名和 MX 记录，把服务器运维交给托管商。
既保有对邮箱的控制又尽量减少麻烦的最佳方案，是拥有自己的域名，把 MX 记录指向你想要的任何托管商，而不是在家里自建服务器。个人博客、视频托管同理：重点是买一个自己控制的域名，然后让 S3、Cloudflare、Hetzner 之类去托管文件。我 15 年前就不再在家自托管邮件了，不想再花精力维护它——只要域名和 MX 记录在自己手里就够了。
jasode查看英文原文
The sweet spot for having control over your email while simultaneously minimizing unforseen headaches is to simply own your domain name and point the MX record to whatever hosting provider you want instead of self-hosting a server at home. Same philosophy for exposing a your personal blog of html files or content like mp4 videos. The sweet spot is to focus on buying a domain name you control. Then let Amazon S3, or Cloudflare, Hezner etc, host your html or mp4 files. I quit self-hosting email at home over 15 years ago. It's just not something I want to babysit anymore because I have other things to focus on. As long as I control the MX record on my own domain, that's really all that's necessary.
历次讨论
同类还值得读
TTY 揭秘（2008）
The TTY demystified (2008)
经典文章深入剖析了 Unix/Linux 中 TTY 子系统的工作原理，包括线路规程、终端驱动、信号与控制字符等机制。
系统与基础设施上首页 11 次 · 2009–2025linusakesson.net编辑精选为什么 GNU grep 这么快
Why GNU grep is Fast
FreeBSD 邮件列表上一篇广为流传的帖子，解释 GNU grep 为什么快：核心在于 Boyer-Moore 字符串搜索算法配合精心优化的内部循环和 I/O，让程序在搜索时“…
系统与基础设施上首页 9 次 · 2010–2022lists.freebsd.orgXplain：为普通人讲解 X11
Xplain – Explaining X11 for the rest of us
《Xplain》是作者（HN 用户 Jasper_）写的一系列 X11 长文，用他在浏览器中重建的 X11 绘图模型做交互演示，讲解 X11 的绘图模型与窗口系统设计。
系统与基础设施上首页 6 次 · 2013–2020magcius.github.io编辑精选旋风教程：为 Linux 创建极小 ELF 可执行文件（1999）
A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux (1999)
breadbox 写于 1999 年的经典教程，主题是如何为 Linux 手工构造并裁剪出体积极小的 ELF 可执行文件。
系统与基础设施上首页 6 次 · 2007–2025muppetlabs.comPostgreSQL 内部原理
The internals of PostgreSQL
《The Internals of PostgreSQL》是一本免费在线书籍，系统讲解 PostgreSQL 的内部实现，包括查询处理、并发控制、WAL、缓冲区管理等核心机制。
系统与基础设施上首页 5 次 · 2017–2025interdb.jp编辑精选