In the photo below shows some failures on DKIM and it uses the same selector as the others used with no issues. Can this be caused by a DSN issue or they could not get the selector for some reason?
Also, there is a temperror on the SPF record. Is this just normal? I see this a lot on my reports. In these cases, if we had DMARC policy enforced would this cause an email to be not accepted? I know for DMARC to align only one of them has to align but what if this happens on both DKIM and SPF?
Hi Steve,
A temperror as its name implies is when the verifier encountered an issue which is likely transient in nature. While there could be multiple cause, the most common one is a DNS related error. The problem could be related to your domain’s DNS, or it could be an issue encountered by the verifier itself.
I would suggest you filter these results by the verdict and review the names of the reporters. If the reporters vary, it is likely an issue with your domain’s DNS. If the problem is isolated to a specific reporter, then it’s more likely that verifier is experiencing issues resolving your domain.
There could also be other factors at play. Are the temperrors isolated only to a single source of email but across many reporters? Then we are likely looking an an issue with a specific source, especially if the source is something like Sendgrid which uses CNAME delegation for the custom return-path and DKIM signatures. The issue could their DNS not yours.
For a more guided support experience, I suggest reaching out to dmarcian support. All of our customers have standard support with any subscription and they can help you by diving into your data to help you with your search.
I hope this helps!
Awesome thanks for this. It’s what I assumed but wanted to make sure it was not an issue with us.
