All Collections
Recent policy changes from Google & Yahoo
Recent policy changes from Google & Yahoo

This article will help you keep up with Google & Yahoo's new email protection policy.

Avipsa Lakhanpal avatar
Written by Avipsa Lakhanpal
Updated over a week ago

Google and Yahoo recently announced an upcoming change to their policies to enhance security, privacy, and overall user experience. These changes aim to create a safer online environment for users and reduce the risks associated with email communication.

As a result, it is crucial for you to ensure that your email practices align with these updated policies to avoid any disruptions in communication. To maintain a seamless and secure exchange of emails, we kindly request your cooperation in adhering to the following guidelines:

1. Email authentication

Ensure that your email server supports industry-standard authentication protocols such as SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance). This helps in verifying the authenticity of the sender and prevents email spoofing.

1.1 SPF (Sender Policy Framework)

What is SPF?

SPF is an email authentication protocol that allows the domain owner to specify which mail servers are authorized to send emails on behalf of their domain.

How to set up SPF:

To implement SPF for your domain:

  • Access your domain's DNS settings.

  • Add a TXT record containing your SPF information. For example:

v=spf1 -all

Customize the "include" values based on the email service providers you use.

1.2 DKIM (DomainKeys Identified Mail)

What is DKIM?

DKIM adds a digital signature to outgoing emails, allowing the recipient to verify that the email was genuinely sent by the domain owner and has not been altered during transit.

How to set up DKIM:

To implement DKIM for your domain:

  • Generate a DKIM key pair, usually provided by your email service provider.

  • Add the public key as a TXT record in your domain's DNS. For example: IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC2Gv1u0Awuzx2pLkoHw84BYz0RL1D8lPKQxdJmy8QF3gIytkTcSkVLrLeQsWMx5bV8TVTIh6aBREwhHwV7PLUzB4JY0ULdnG0sW/W3UrcLCYQWqBA2vq8+jOuj6DUMcBoFwP5rtbCm0LiPy1f+yaq2KFEnq5XkFDnETUpTTekQIDAQAB"

Adjust the "selector" and "p" values accordingly.

1.3 DMARC (Domain-based Message Authentication, Reporting, and Conformance)

What is DMARC?

DMARC builds on SPF and DKIM to provide a policy framework for domain owners to specify how email receivers should handle messages that fail authentication.

How to set up DMARC:

To implement DMARC for your domain:

Create a TXT record in your DNS with the DMARC policy. For example: IN TXT "v=DMARC1; p=reject;;; fo=1"

Customize the "p" value based on your desired policy (none, quarantine, or reject).

Additional Tips 💡

1. Regularly monitor DMARC reports and adjust policies accordingly.

2. Test your SPF, DKIM, and DMARC configurations using online tools.

3. Keep your DNS records up to date as your email infrastructure evolves.

If you encounter any challenges during the implementation process or have questions, please reach out to your Email Administrator/ Email Service Provider.

2. Enable Easy Unsubscription

Email recipients must be able to unsubscribe from unwanted emails without any hassle. It should just take one click.

3. Ensure you are sending a wanted email

Based on email sender guidelines from Google, you should maintain a spam rate of 0.1% or less to verify recipients of your email successfully receive your emails.

If your spam rate is consistently 0.3% or more, you may experience email performance issues, including delays, spam filtering, or bounces.

Did this answer your question?