DMARC is an email authentication standard that is used to protect a domain from fraudulent email. It builds on top of SPF and DKIM.
Why should I use DMARC?
Simply put, DMARC adds an additional layer of domain-based authentication for emails sent from your domain. Used jointly with SPF and DMARC, it tells the receiving mail server how to handle emails that do not pass SPF or DKIM validation.
Thanks to clear instructions on how to handle potential spoof emails, your customer's email server has fewer reasons to treat your messages as junk or spam.
Check Postmark's guide on DMARC if you wish to learn more technical details about how DMARC works.
Setting up DMARC
Make sure you have access to your domain control panel. You would need to create or update DNS records in order to setup DMARC.
Open your Helprace Admin Panel.
Go to Settings > TICKETS > Mailboxes.
Open a mailbox.
Expand the DMARC section. You'll see a suggested TXT type record there.
Open your domain control panel and add the suggested record there, e.g.:
_dmarc.acme.com TXT v=DMARC1; p=none; sp=none
Replace "acme.com" with the domain of your mailbox (e.g. if your mailbox is firstname.lastname@example.org, the domain would be mycompany.com).
The record may include additional data at the end (as long as it has a valid (v=DMARC1; p=none; sp=none) like in the example above).
In some domain control panels you don't need to specify the domain. You can use "_dmarc" instead of "_dmarc.acme.com".
Instead of filling out a text line, you may be required to fill in a form. In that case:
- Type / Record Type: TXT Record
- Host / Hostname: _dmarc
- Text / Value / Content: v=DMARC1; p=none; sp=none
- Time to Live / TTL: 3600
Once you've updated your DNS records, you can go back to the mailbox and click Test button to ensure that DMARC configuration is valid. It should turn to a green checkmark if everything is working properly. Please note, it can take up to 24 hours for DNS changes to propagate (usually this happens within an hour).
If you don't think you have access to your site DNS settings, pass this information on to your website administrator or the IT guy. They will know what to do.