Create a DMARC policy
Domain-based Message Authentication, Reporting & Conformance (DMARC) is used in conjunction with SPF and DKIM to combat email spoofing. Spoofing occurs when a scammer uses your domain in the From field of an email to impersonate one of your users. DMARC uses a policy that is given by your email provider. This policy tells the receiving email host how to treat emails sent from your domain based on the criteria that you set. This mechanism also gives visibility into reports on what your domain is sending, and how receiving hosts are treating that mail.
This article shows how to create a DMARC policy to use with Cloud Office.
- Applies to: Administrator
- Difficulty: Moderate
- Time needed: 24-48 hours for DNS record changes to propagate
- Tools required: DNS host Administrator access
For more information about prerequisite terminology, see Cloud Office support terminology.
If you prefer a video tutorial, please see Rackspace Email - DMARC / DKIM: What It Is & How to Setup .
DMARC enforces SPF and DKIM. DMARC is useful only if you have already set up SPF and DKIM records. Before creating your DMARC policy, you must first create an SPF record policy, then create a DKIM record, and lastly create a DMARC record policy.
Considerations for DMARC
To set up DMARC the way that works best for your needs, answer these questions:
How should questionable mail be handled?
Decide whether questionable email should be rejected outright or should be classified as a “soft fail,” which means that the email is further scrutinized or sent to spam.
Who should receive DMARC reports?
When the receiving host processes mail that comes from the domain, the host generates reports. These reports are sent to the email address specified in the DMARC policy.
Parts of a DMARC policy:
Each part of the policy is defined as follows:
- dmarc: identifies the TXT record as a DMARC policy.
- v=DMARC1 indicates the version of DMARC used.
- p=quarantine: is the policy action.
- none: Do nothing/reporting only
- quarantine: Treat the mail as spam
- reject: Refuse mail that fails DKIM and SPF
- rua= identifies the destination for the aggregate reports.
- pct=100 specifies how much traffic should be subject to policy validation.
Create a DMARC policy in your DNS settings
Note: If your DNS is not hosted with Rackspace, you need access to your DNS provider to add the DMARC policy. If you do not know where your DNS is hosted, see Find DNS host.
To add your DMARC policy as a TXT record in the Control Panel, follow these steps:
- Log in to the Cloud Office Control Panel.
- In the Domains section of the home page, click the DNS settings link.
- On the DNS Settings page, click the domain for which you want to add this record.
- Under the Advanced Settings section, select DNS records.
- Under Hosting Records, click on Add Additional Record.
Select TXT Record for the record type, and enter the following values, replacing the email address example with your chosen reporting address:
v=DMARC1; p=none; rua=mailto:CHOSENemail@yourdomain.com
- Priority: NA
- TTL: 3600 seconds or lowest allowed
- Click Add Record
Your new settings take 24 to 48 hours to propagate. For more information on propagation, see DNS propagation.
Select an aggregator
Your DMARC policy is more valuable when you use an aggregator to help filter the content of the reports that are returned. Without an aggregator, the reports are in an XML format and are virtually unreadable. An aggregator formats this information and sends out weekly reports to the email address specified. The weekly report contains the sending source (domain or IP address) and information about whether the message passed or failed SPF and DKIM. This information enables you to monitor your domain’s activity and helps to prevent spoofing and domain abuse.
Following are some top reporting aggregators, based on suggestions from https://dmarc.org/resources/products-and-services/:
Continue the conversation in the Rackspace Community.
©2017 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License