Understanding Gmail and Yahoo DMARC requirements

Google and Yahoo announced requirements that bulk senders must have DMARC in place beginning February 2024.

Google and Yahoo both recognize the importance of email and are taking steps toward making it more safe and secure. By focusing on email validation, they are helping prevent unwanted spam and potential bad actors from reaching their customers’ inboxes.

• Overview of DMARC 
• Accommodating email records
  • Understanding a DMARC structure
• Adding a DMARC record
  • Locating your account email
• Ensuring your account has proper validation records
• Additional information

Overview of a DMARC

Domain-based Message Authentication, Reporting & Conformance (DMARC) is an email authentication, policy, and reporting protocol. It uses Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) protocols, adding a connection to the domain name for recipient handling of authentication failures and reporting from receivers to senders.  Furthermore, it is to improve and monitor the protection of the domain from fraudulent email.

Sending from a domain with DMARC in place has the benefit of improving inbox placement. A DMARC record helps ISPs identify you as a sender who is serious about following established email standards and reducing your spam liability.

Back to top

Accommodating email records

Your messages pass SPF using the same domain as your message From: header. This is the Return-Path value within email headers. This header value is called the bounce domain, envelope-from, or MailFrom.

Beginning February 2024, emails must pass DMARC through these requirements:

• Authenticating with SPF.
• Authenticating with DKIM.
• Published DMARC TXT record.

DMARC

Subdomain	_dmarc
Record Data	v=DMARC1; p=none; (Minimum required)

SPF

TXT	Root Domain
Record Data	v=spf1 include:_spf.emfwd.name-services.com MX ~all Note: For the Hosted Email platform.

Back to top

Understanding a DMARC structure

Tag	Value	Translation
V	DMARC1	The DMARC version should always be DMARC1. Note: An incorrect DMARC tag would cause the entire record to be ignored.
P	none	The policy is applied to emails that fail the DMARC check. Authorized values: none, quarantine, or reject. None is used to collect feedback and gain visibility into email streams without impacting existing flows.
rua	mailto:[e-mail]	The list of URIs for receivers to send XML feedback to.
ruf	mailto:[e-mail]	The list of URIs for receivers to send reports to.

Back to top

Adding the DMARC record

1. Locate the domain you want to manage by clicking Domains followed by My domains.
   
   
2. Search for the domain or choose from the list.
   
   
3. Choose Host records from the manage domain dropdown.
   
4. Enter the records in the text field and hit Save.
   Note: Replace [e-mail] with your email address. 
   

   Host name	Address
   _dmarc	v=DMARC1; p=none; rua=mailto:[e-mail]; ruf=mailto:[e-mail];fo=1
   	v=spf1 include:_spf.hostedemail.com ~all

   
   

Back to top

Locating your account email

Enom uses your account email to send out account and system notifications.  Adding the DMARC record to your account email domain is required to ensure notifications are sent properly. 

1. Log into your Enom account.
2. Click My account and Account settings.
   
3. The domain of your account email will need the DMARC records, and this SPF record "v=spf1 include:_spf.hostedemail.com ~all"
   Note: If the account email domain cannot pass email validation checks, registrants may not receive system notifications.  Remove the quotation marks from the SPF record.
   

Back to top

Ensuring your account has proper validation records

Enom uses your account email to send out account and system notifications.  Adding the DMARC record to your account email domain is required to ensure notifications are sent properly. 

1. Log into your Enom account.
2. Click My account and Account settings.
   
3. The domain of your account email must have updated validation records located here DMARC records.  Additionally the SPF record v=spf1 include:_spf.hostedemail.com ~all is also required. 
   Note: If the account email domain cannot pass email validation checks, registrants may not receive system notifications. 
   

Additional information

• Yahoo - An Update on Enforcing Email Standards
• Google - New Gmail protections for a safer, less spammy inbox
• Dmarcian - Understanding Gmail and Yahoo DMARC Requirements
• The Difference in DMARC Reports: RUA and RUF
• DMARC Record Checker

Back to top