大网数据广告活动
网站运营与故障问答

Is DMARC relaxed alignment for SPF/DKIM bad?

· 52CE 我爱测

After studying authentication mechanisms available to prevent e-mail spoofing, still I don't understand how to choose between the relaxed alignment and the strict alignment in DMARC for SPF and DKIM, apart from parent/child domai…

问题原文

原帖链接 · Vincent · CC BY-SA 4.0

After studying authentication mechanisms available to prevent e-mail spoofing, still I don't understand how to choose between the relaxed alignment and the strict alignment in DMARC for SPF and DKIM, apart from parent/child domain considerations. I did not find useful information in RFC 7489 on an eventual weakness of the relaxed alignment. Though I understand perfectly how these 2 alignments work, my questions are:

  1. Is it bad to use a relaxed alignment compared to the strict alignment?
  2. Are there any weaknesses when using the relaxed alignment with SPF, DKIM, or both?

已采纳解答

原帖链接 · Reinto · CC BY-SA 4.0

Relaxed Alignment let's you authenticate your FROM domain by using a subdomain in your DKIM signature (d=sub.domain.tld) or Return-Path address ([email omitted]). This is very useful for delegating subdomains to third parties to authenticate on your behalf. There are many reasons one might choose to: bounce-handling capabilities of the 3rd party, or; the organizational domain's SPF record exceeding the DNS Lookup limit (max 10 lookups allowed during SPF check), and more.

The consequence is that any of those parties allowed to authenticate on behalf of the subdomain can send from the organizational domain in the FROM address, if the DMARC alignment policies are set to relaxed, which is the default. Also, those 3rd parties will be able to use other subdomains, existing or non-existing, in the FROM address as well, if there is not a DMARC record published for the subdomain. Because, the check will fall back to the organizational domain's DMARC record if none is present at the subdomain used in the FROM field.

I'm not entirely sure if this constitutes a weakness.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2021-06-08)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。