Record authentication evaluations at the receiving trust boundary

Frame this document as a source-led configuration and assurance check: Record authentication evaluations at the receiving trust boundary. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 8601 — Message Header Field for Indicating Message Authentication Status from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• Authentication-Results assertions are trustworthy only when producer and consumer are connected through the receiving administrative domain’s configured trust boundary. The research record locates this support at Section 1.2 (Trust Boundary).
• The authentication service identifier is unique within its administrative domain and lets downstream consumers decide whether to use or ignore the recorded result. The research record locates this support at Section 2.5 (Authentication Service Identifier Field).
• At ingress, an MTA removes a forged Authentication-Results field that claims an internal identifier but did not arrive directly from a trusted MTA. The research record locates this support at Section 5 (Removing Existing Header Fields).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling and the conditions the source actually describes.

What the source does not establish

This RFC evidence supports only the named mail-protocol decision; it does not prove provider support, deliverability, or compliance for a particular flow. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Section 1.2 (Trust Boundary), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 2.5 (Authentication Service Identifier Field), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 5 (Removing Existing Header Fields), which observable configuration, record, or test can confirm applicability here?
• Within sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, which versions, roles, and configuration states define the review population?
• Could authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Tie each conclusion back to Section 1.2 (Trust Boundary); Section 2.5 (Authentication Service Identifier Field); Section 5 (Removing Existing Header Fields) and to observable material such as sanitized messages, DNS records, SMTP transcripts, authentication results, policy evaluation, and delivery or rejection logs. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• RFC 8601 — Message Header Field for Indicating Message Authentication Status — RFC Editor / Internet Engineering Task Force