Aggregate SMTP TLS policy outcomes into daily JSON reports

Treat this document as a focused evidence review: Aggregate SMTP TLS policy outcomes into daily JSON reports. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 8460 — SMTP TLS Reporting from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An SMTP TLS aggregate report is I-JSON containing report metadata, applied policy, aggregate session counts, and optional per-failure details. The research record locates this support at Section 4 (Reporting Schema).
• A report should cover one UTC day, and senders should delay delivery to avoid overloading the report processor. The research record locates this support at Section 4.1 (Report Time Frame).
• TLS reports may be delivered as email or by HTTP POST, using the transport-specific formats defined for each route. The research record locates this support at Section 5 (Report Delivery).

Only the traced statements above are asserted as source facts. Apply the review to sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling after confirming that the source and deployed context match.

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 4 (Reporting Schema), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 4.1 (Report Time Frame), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 5 (Report Delivery), 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. Begin by recording scope and current state before deciding whether a change is warranted. 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.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers before and after the test, and store only sanitized operational evidence.

Verification and evidence

Build a reproducible chain from Section 4 (Reporting Schema); Section 4.1 (Report Time Frame); Section 5 (Report Delivery) to the observed environment. Useful domain evidence includes sanitized messages, DNS records, SMTP transcripts, authentication results, policy evaluation, and delivery or rejection logs; label every item with scope, timestamp, collector, and stable identifier.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• RFC 8460 — SMTP TLS Reporting — RFC Editor / Internet Engineering Task Force