Closed schleup closed 1 year ago
Thank you for the report, I'll fix it soon.
I have just fixed this issue: 20777cf6a8edecf0e123d8702a7ee3e6697928f5
Now reports are accepted without errors. The fix only adds a new rule and suggests updating the database. This is the first step. Then I'll add code to save and display this policy. So you will have time to update the database.
Thank you :-)
Just tested it, the Google reports are accepted and evaluated now.
I implemented saving and displaying this policy with the latest commit: 4f4ba5da3694d67cee30bac4ea24f513d3e56680
Thank you, this works perfectly as well:
I upgraded from 1.3 to 1.7 and this is still present. The fix is pushed into a release?
This fix isn't in the latest release yet.
@ntnlabs, I just released version 1.8 which includes this fix.
When fetching reports from noreply-dmarc-support@google.com I encounter an error: Unknown tag: NP
Most likely this is caused by the NP policy used in Google's records, like:
In the code I find all policies from the snippet but NP is missing. Seems this is a new policy, since it's mentioned in the JPAAWG 2022 Keynote as new:
https://dmarc.org/presentations/JPAAWG-2022-Keynote-2.pdf
By the way, the domain concerned doesn't use the NP policy...
####. 300 IN TXT "v=DMARC1; p=quarantine; rua=mailto:####; ruf=####; rf=afrf; pct=100"
I'm using the latest version v1.7 from Github.