Error when opening DMARC reports
I get this error when I try to view the DMARC reports for one of my domains:
Error:
result[51].Records[0].AuthResults.DKIM[0].Result: unknown value unknown for named strings DKIMResult
@soheilpro Which version are you using? Looks similar to #161, but related to DKIM not SPF.
Could you post the DMARC report (see #176 as example)?
Here's the report:
{
"ID": 870,
"Domain": "[REDACTED]",
"FromDomain": "dmarc.inexio.net",
"Version": "",
"ReportMetadata": {
"OrgName": "inexio.net",
"Email": "[email protected]",
"ExtraContactInfo": "",
"ReportID": "[REDACTED]:1726351500",
"DateRange": {
"Begin": 1726264800,
"End": 1726351200
},
"Errors": null
},
"PolicyPublished": {
"Domain": "[REDACTED]",
"ADKIM": "r",
"ASPF": "r",
"Policy": "reject",
"SubdomainPolicy": "reject",
"Percentage": 100,
"ReportingOptions": ""
},
"Records": [
{
"Row": {
"SourceIP": "54.240.9.40",
"Count": 1,
"PolicyEvaluated": {
"Disposition": "none",
"DKIM": "pass",
"SPF": "fail",
"Reasons": null
}
},
"Identifiers": {
"EnvelopeTo": "",
"EnvelopeFrom": "",
"HeaderFrom": "[REDACTED]"
},
"AuthResults": {
"DKIM": [
{
"Domain": "[REDACTED]",
"Selector": "",
"Result": "unknown",
"HumanResult": ""
},
{
"Domain": "amazonses.com",
"Selector": "",
"Result": "unknown",
"HumanResult": ""
}
],
"SPF": [
{
"Domain": "mail.[REDACTED]",
"Scope": "",
"Result": "softfail"
}
]
}
},
{
"Row": {
"SourceIP": "54.240.9.40",
"Count": 1,
"PolicyEvaluated": {
"Disposition": "none",
"DKIM": "pass",
"SPF": "fail",
"Reasons": null
}
},
"Identifiers": {
"EnvelopeTo": "",
"EnvelopeFrom": "",
"HeaderFrom": "[REDACTED]"
},
"AuthResults": {
"DKIM": [
{
"Domain": "[REDACTED]",
"Selector": "",
"Result": "unknown",
"HumanResult": ""
},
{
"Domain": "amazonses.com",
"Selector": "",
"Result": "unknown",
"HumanResult": ""
}
],
"SPF": [
{
"Domain": "mail.[REDACTED]",
"Scope": "",
"Result": "softfail"
}
]
}
}
]
}
Indeed, the "Result": "unknown", isn't valid.
The problem (that mox shows an error message) is fixed with https://github.com/mjl-/mox/commit/a2c9cfc55be686f1e650d9150ae5a06268a23690, which still has to make it into a release...
This is now in release v0.0.12, so closing this issue. Feel free to reopen if the problem persists. Thanks for reporting!