Expanding on DMARC #2102
mrinc
started this conversation in
Feature suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I thought I'd expand on #424
DMARC reports can now be sent from some mail receivers which can carry information about mails - an example would be #2101
The DMARC reports are send in zip files with a single xml file like this:
So what I think could happen on a DNS setup, is checking if DMARC is already setup on the domain.
In the case nothing is setup, is to show the DMARC setup info automatically with how the user can set it up.
If DMARC is already setup, then it could be expanded on to show DMARC info/recommendations (like reports).
So postal could have a mail route for incoming emails -
dmarc-reports@{postaldomain}
.There are also forensic reports, but I haven't received one, however the aggregate reports are very helpful.
This is the DMARC report record we use:
v=DMARC1; p=reject; sp=reject; aspf=s; rf=afrf; pct=100; adkim=s; fo=1; ri=86400; rua=mailto:[email protected]; ruf=mailto:[email protected]
So inbound mail to those addresses could be handled by postal, and then parse the reports - to display them under the domain.
A way to differenciate different domains assigned to different orgs, is to use the dkim selector, else a general reports tab (the report could be a component, so development is minimal)
From there, lets say you're seeing a lot of reports come in from google.com (like us) for dkim failures, you could notify the admins or hold any emails to google.com pending additional setup or what not - thus eliminating the chance even more of being marked for spam.
Beta Was this translation helpful? Give feedback.
All reactions