You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per [DNS], a TXT record can comprise several "character-string"
objects. Where this is the case, the module performing DMARC
evaluation MUST concatenate these strings by joining together the
objects in order and parsing the result as a single string.
I believe that it means concatenating several character strings that are only in one record like in:
Section 6.6.3. Policy Discovery explains how results with multiple records should be treated:
Mail Receivers MUST query the DNS for a DMARC TXT record at the
DNS domain matching the one found in the RFC5322.From domain in
the message. A possibly empty set of records is returned.
Records that do not start with a "v=" tag that identifies the
current version of DMARC are discarded.
If the set is now empty, the Mail Receiver MUST query the DNS for
a DMARC TXT record at the DNS domain matching the Organizational
Domain in place of the RFC5322.From domain in the message (if
different). This record can contain policy to be asserted for
subdomains of the Organizational Domain. A possibly empty set of
records is returned.
Records that do not start with a "v=" tag that identifies the
current version of DMARC are discarded.
If the remaining set contains multiple records or no records,
policy discovery terminates and DMARC processing is not applied
to this message.
I will contribute a fix for this issue.
The text was updated successfully, but these errors were encountered:
mimi89999
added a commit
to mimi89999/go-msgauth
that referenced
this issue
Jan 15, 2025
Hello,
I noticed that when a domain has multiple TXT records on the
_dmarc
subdomain like:dmarc-lookup
will concatenate the records and the results will depend on the order in which the records were received:The RFC states that:
I believe that it means concatenating several character strings that are only in one record like in:
where a string was split.
Section 6.6.3. Policy Discovery explains how results with multiple records should be treated:
I will contribute a fix for this issue.
The text was updated successfully, but these errors were encountered: