DMARC and deliverability
Correct DNS and responsible sending improve trust, but no service can guarantee inbox placement or message reading.
Inbound routes
Create a DMARC or TLS report route in Console, then copy its DNS records to each domain. Review the processed results on the corresponding reports page.
TLS reports
Review TLS delivery results for each policy. Failure categories can overlap; their counts must not be added together. Report sources are processed in memory and discarded. Only useful report information is retained.
Authentication records
SPF authorises sending services, DKIM signs outgoing messages for the domain, and DMARC defines alignment and reporting policy. Copy the deployment-specific records from Console rather than from a generic example.
Alignment and reports
DMARC evaluates whether authenticated identities align with the visible From domain. Aggregate reports show participating sources and authentication results; they do not contain ordinary message bodies.
Responsible sending
Send only lawful, expected messages to valid recipients. Keep lists current, make identity and purpose clear, avoid deceptive content, and act on permanent delivery failures and recipient requests.
Delivery outcomes
Queued means accepted for processing. Sent means the next destination accepted that recipient delivery. Deferred is temporary, and failed is final. Acceptance does not guarantee inbox placement, reading, or a later reply.