Send "none" instead of "pass" as the DMARC report disposition #76

Merged

jcoffey-dev merged 1 commits from fix/dmarc-disposition-compat into main

2026-09-28 05:48:23 +00:00

Author	SHA1	Message	Date
jcoffey-dev	e1e8a9aeb0	Send "none" instead of "pass" as the DMARC report disposition ci / build (pull_request) Successful in 16m34s Details ci / fork-checks (pull_request) Successful in 52s Details Cloudflare's DMARC report intake rejects every aggregate report we send with "555 5.7.1 invalid_report_schema". Bisected against the live endpoint: the only element it objects to is <disposition>pass</disposition>, the value RFC 9990 added for mail that passed DMARC under an enforcing policy. The RFC 9990 namespace, <np>, <discovery_method>, <testing> and a missing <pct> are all accepted, and a report that differs only in using "none" there goes through. "none" (no action taken) is valid under both RFC 9990 and RFC 7489 and says the same thing to the reader, so reports now go out with it. The stored report keeps "pass"; only the serialized copy changes.	2026-09-27 22:31:13 -07:00

Author

SHA1

Message

Date

jcoffey-dev

e1e8a9aeb0

Send "none" instead of "pass" as the DMARC report disposition

ci / build (pull_request) Successful in 16m34s

Details

ci / fork-checks (pull_request) Successful in 52s

Details

Cloudflare's DMARC report intake rejects every aggregate report we
send with "555 5.7.1 invalid_report_schema". Bisected against the live
endpoint: the only element it objects to is <disposition>pass</disposition>,
the value RFC 9990 added for mail that passed DMARC under an enforcing
policy. The RFC 9990 namespace, <np>, <discovery_method>, <testing> and
a missing <pct> are all accepted, and a report that differs only in
using "none" there goes through.

"none" (no action taken) is valid under both RFC 9990 and RFC 7489 and
says the same thing to the reader, so reports now go out with it. The
stored report keeps "pass"; only the serialized copy changes.

2026-09-27 22:31:13 -07:00