lol DMARC is one record.

It doesn't have to be just one record, but it doesn't have to be more than one record either.

DMARC is layered across (/is useless without) two other protocols (SPF, DKIM), both of which also require DNS records.. there's no way to DMARC with one record.. unless you're excluding those SPF and DKIM records in your count. You /could/ DMARC with two records: DMARC+SPF, or DMARK+DKIM but it's ill-advised - use all three. (Ignoring host hierarchy/cname delegation, you can have far more records)

▲

bawolff 39 minutes ago | parent | next [-]

Were you previously sending email without either DKIM or SPF?

Because i doubt that has worked at all in the last decade.

	▲	gnabgib 37 minutes ago \| parent [-]
		Are you replying to the wrong comment? No on all counts.

▲

jared_stewart 3 hours ago | parent | prev [-]

I suppose I'm splitting hairs.

Yes, a proper email authentication stack has DMARC + SPF + DKIM. But each of these is a separate protocol.

This also doesn't take into consideration the other protocols that have arisen BIMI, APRF, MTA-STS / TLS-RPT and are at even lower levels of adoption.

	▲	gnabgib 3 hours ago \| parent [-]
		MTA-STS is useful (but it's about helping receivers by demanding mail is sent encrypted, not senders with delivery). BIMI is a pay-to-spam protocol that helps senders, you can add a rule to postfix to mark it as such. APRF is a draft, and likewise helps senders, not receivers.. not sure why anyone would want to adopt this standard. A little closer to DMARC reports, but sharing PI that you owe no sending server.