As a Enhance end user and server administrator I would like Enhance to add DMARC to the Email Deliverability interface in Enhance in order to ensure that all available email authentication options are presented to me in one place.
Add DMARC to the Email
+1
+1
6 days later
Aliysa_Enhance added the Email tag.
a month later
Note: You can always add DMARC by adding a TXT record manually through the panel.
But implementing a UI there is better and helps avoid mistakes.
- Edited
What DMARC options do you think Enhance should allow us to configure? DMARC is very easy to add, but it's essential DKIM is configured first.
"v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"
Is a basic record, but which policy do you think Enhance should set? Which rua email address?
DMARC is great, and you should be using it.. but all these requests for one click setup of things that require more understanding are a bit of waste of the UI space and Enhance time right?
Such features are not difficult to implement, and there is plenty of space for them. If Enhance decided to support email, it would be great if features like DMARC could be enabled from the panel.
_dmarc.example.com. IN TXT "v=DMARC1; p=none; rua=mailto:reports@example.com; ruf=mailto:forensic@example.com; fo=1; pct=100"
.. and you think customers would be fine with that kind of DMARC record? Would they have reports@ and forensic@ already setup? Would they understand the "raw" DMARC reports?
I don't think so.. but.. you are welcome to your own opinion.
It's true that not all customers may be familiar with DMARC records or have the necessary setups in place for reports and forensic data. Providing clear instructions and support can help bridge this gap and ensure successful implementation. Ultimately, it depends on the level of technical expertise and support available to the customers.
Did you just use ai to reply to me? 
No, however, my English is not very good, and I'm using a translator.
I think Enhance should not create a DMARC record itself, but give the user the possibility to create one as simple as possible. Similar to what cPanel does, for example:
This way, every user can decide for themselves whether they want to set a DMARC record and if they do, then they have to deal with it and consider what this record should look like.
Yeah, DMARC isn't something that can just be automatically setup. There are too many options to it.
Even enterprise services like O365 and Google Workspaces don't provide any DMARC setup, that's up to you.
It can be automated by adding it to the DNS template. We do it this way, and it is working perfectly. For us, we have always used a host (us) level dmarc. We set it to a specific email address which we can easily search and sort for any issues.
In using DMARC records since they were first recommended, we have had exactly one customer request that the dmarc be specific (email addresses) to their domain.
These days the DMARC is becoming more essential, so I believe it is better to setup the generic one with our email than to not have it. If a customer needs it tailored to their needs, they typically already know what is going on, and will just modify it.
Go to Settings | Platform | DNS Zone Templating
And set it up there.
if you dont send them to a third party to aggregate the reports its not that useful to read xml 