DKIM2 docs: reply-code guidance is §10.4 not §11.1; any-one-passes ve…

[juliebin]

…rdict is Momentum policy, not §11.6

• Give your PR a recognizable title. For example: "FE-123: Add new prop to component" or "Resolve Issue Create new-pricing-increases-costs #123: Fix bug in component"
• Your PR title will be visible in changelogs

What Changed

• What changes does this PR propose?
• Provide screenshots or screen recordings for any visual changes.

How To Test or Verify

• Describe any steps that may help reviewers verify changes.
• Anything beyond basic unit testing, such as assistive tech usage, or special interactions.

PR Checklist

Below are some checklists to follow for the correct procedure in different circumstance. The first list ("All PRs Checklist") should be followed for ALL PRs. The next 2 are additive to this list depending on what type of PR you are using.

For example: If you are submitting a content change to one of the support documents, your checklist would include the:

• "All PRs Checklist"
• AND the "Content Changes Checklist

If you are submitting a feature addition, enhancement, or bug fix, your checklist would include the:

• "All PRs Checklist"
• AND the "Development Changes Checklist"

All PRs Checklist

• Give your pull request a meaningful name.
• Use lowercase filenames.
• Apply at least one team label according to which team is the content expert (ie. team-FE or team-SAZ)
• Pull request approval from the FE team or content experts (see label applied above) that isn't the content creator.

Content Changes Checklist

• Check that your article looks correct in the preview here or in a Netlify deploy preview.
• Check the links in your article.
• Check the images in your article (if there are any)
• Check to make sure you are using markdown appropriately as outlined in examples/article.md in the root of the project directory and on the momentum doc's preface article
• Check to make sure the Copy and Tone Guidelines are followed.

Development Changes Checklist (some checks are automatic github actions and will not be listed here. ie. "all tests pass")

• The appropriate tests are created in cypress/ directory in the root of the project
• The lighthouse score is passing according to the FE Support Docs' Service Outline SLI/SLOs

---

Note

Low Risk
Documentation-only corrections to spec section references and product-behavior clarity; no runtime or API changes.

Overview
DKIM2 verification docs retarget SMTP reply guidance from §11.1 to §10.4: section title, table headers, inline references, anchor link (#smtp-response-codes-104-guidance), and the example hook comments. The permerror row no longer claims MUST NOT 4xx in the suggested-action column; key rules now state only fail (crypto failure) MUST NOT use 4xx, while other permanent errors (permerror) SHOULD use 5xx.

DKIM2 signing docs clarify that when multiple sig-sets are present, “overall verdict passes if any one validates” is Momentum’s behavior (not presented as generic §11.6 wording), with minor line wrapping on the combined DKIM2-Signature description.

Both pages bump lastUpdated to 07/27/2026.

^{Reviewed by Cursor Bugbot for commit 8a5a7e7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[netlify]

✅ Deploy Preview for support-docs ready!

Name	Link
🔨 Latest commit	8a5a7e7
🔍 Latest deploy log	https://app.netlify.com/projects/support-docs/deploys/6a68d62495ed8f000716b798
😎 Deploy Preview	https://deploy-preview-863--support-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.