resolution_worksformetype_defect | by mike@mtcc.com
failure reports are currently delivered by email, but the document doesn't have any guidance about authentication either for the sender, or what the receiver should do if it doesn't get a valid DKIM signature or SPF pass. there should be normative language which specifies their respective behaviors.
"Email that delivers the DMARC failure reports of any kind MUST be either signed with a valid DKIM signature from the domain it purports to come from, or must pass an SPF validation [mat: wrong parlance most likely... help]. Receivers SHOULD discard the email report if they cannot be validated as authentic from the sending domain."
Issue migrated from trac:98 at 2022-01-24 16:53:04 +0000
resolution_worksforme
type_defect
| by mike@mtcc.comfailure reports are currently delivered by email, but the document doesn't have any guidance about authentication either for the sender, or what the receiver should do if it doesn't get a valid DKIM signature or SPF pass. there should be normative language which specifies their respective behaviors.
"Email that delivers the DMARC failure reports of any kind MUST be either signed with a valid DKIM signature from the domain it purports to come from, or must pass an SPF validation [mat: wrong parlance most likely... help]. Receivers SHOULD discard the email report if they cannot be validated as authentic from the sending domain."
Issue migrated from trac:98 at 2022-01-24 16:53:04 +0000