充满服务器的整个数据中心的 DMARC 合规性
我们正在进行一个项目，使我们的所有邮件源（包括代表我们发送的第三方）都符合 DMARC。我们遇到了一个障碍，即整个数据中心充满了发送邮件的服务器（通常只是状态更新或错误）。如果邮件的发件人地址为 <[电子邮件受保护]>我们有很多，而且几乎每周都会添加新的，那么如何让这些合规呢？
我对 DKIM 和 SPF 的理解是，我们需要每个主机一个 DNS 条目，因为接收邮件服务器根据发件人地址的 FQDN 检查这些记录。
有没有合理的方法来继续使用<[电子邮件受保护]>作为发件人地址，并且仍然使这 200 多个（且不断变化的）服务器符合 DMARC？
We're in the midst of a project to make all of our mail sources, including third parties that send on our behalf, DMARC compliant. We've run into a snag, namely an entire data center full of servers that send mail (usually just status updates or errors). If the mail's from address is <[email protected]> and we have many of them, and there are new ones added almost weekly, then how do get these compliant?
My understanding of DKIM and SPF, is that we'd need a DNS entry per host, because the receiving mail server checks on those records based on the FQDN of the from address.
Is there a reasonable way to keep using <[email protected]> as the from addresses and still make these 200+ (and changing) servers DMARC compliant?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，这就是 DMARC 的“轻松”模式的用途。您可以通过将这些元素添加到 DMARC 记录来设置 SPF 和 DKIM 匹配：
但是，这是默认行为，因此您实际上根本不需要添加它们！
在此模式下，来自
[电子邮件受保护] 的邮件code> 将是一个轻松的匹配对于domain.tld。Yes, this is what DMARC's "relaxed" mode is for. You can set that for both SPF and DKIM matching by adding these elements to your DMARC record:
However, this is the default behaviour, so you don't actually need to add them at all!
In this mode, a message from
[email protected]would be a relaxed match fordomain.tld.