{"id":9372,"date":"2024-01-11T09:41:13","date_gmt":"2024-01-11T08:41:13","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/us\/new-authentication-requirements-for-gmail-and-yahoo-what-senders-of-large-email-volumes-need-to-consider-now"},"modified":"2024-05-07T18:56:09","modified_gmt":"2024-05-07T16:56:09","slug":"new-authentication-requirements-for-gmail-and-yahoo","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/us\/new-authentication-requirements-for-gmail-and-yahoo\/","title":{"rendered":"New authentication requirements for Gmail and Yahoo: What senders of large email volumes need to consider now"},"content":{"rendered":"\n

Google<\/a> and Yahoo<\/a> are getting serious: for senders who send more than 5,000 emails per day, stricter requirements regarding the authentication of messages will apply starting February 2024. In order to further reduce the amount of spam in inboxes, the providers are making standards such as SPF, DKIM, and even DMARC mandatory for their free email services.<\/p>\n\n\n\n

So, especially for companies that send large volumes of emails to end customers via business applications<\/a>, there is an urgent need for action. Below we have compiled a summary of what exactly you need to bear in mind.<\/p>\n\n\n\n

Which authentication changes you should make immediately<\/h2>\n\n\n\n

To ensure proper authentication, you should make the following changes to the DNS entry for your domains:<\/p>\n\n\n\n

SPF<\/h3>\n\n\n\n

SPF (Sender Policy Framework) is a type of DNS TXT record that allows senders to specify which IP addresses are authorized to send email on behalf of a particular domain, for example<\/p>\n\n\n\n

v=spf1 ip4:1.2.3.4 ip4:2.3.4.5 include:thirdparty.com -all  <\/em><\/p>\n\n\n\n

This indicates that a recipient should only accept emails from a domain that either originates from IP address 1.2.3.4 or 2.3.4.5 or from an IP address that belongs to the DNS record of “thirdparty.com”.<\/p>\n\n\n\n

DKIM<\/h3>\n\n\n\n

DKIM is a process to validate sending domain names associated to email messages through cryptographic authentication. It achieves this by inserting a digital signature into the message header which is then verified by the receiving host to validate the authenticity of the sending domain.\u00a0 There are plenty of website that can help you create DKIM DNS header, for example socketlabs.com<\/a>

<\/p>\n\n\n\n

\"Free\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Free web-based DKIM generators can be helpful in creating a corresponding DNS header. Source: socketlabs.com<\/figcaption><\/figure>\n\n\n\n

DMARC<\/h3>\n\n\n\n

DMARC is an open email authentication protocol that provides domain-level protection of the email channel. DMARC authentication detects and prevents email spoofing techniques used in phishing, business email compromise (BEC), and other email-based attacks.<\/p>\n\n\n\n

In addition to SPF and DKIM, DMARC is also a technology being used to make the header \u201cfrom\u201d domain trustworthy. The domain owner publishes a DMARC record in the DNS to tell receivers what to do with emails that fail authentication.<\/p>\n\n\n\n

For example<\/p>\n\n\n\n

v=DMARC1; p=quarantine; rua=mailto:rua@example.com; ruf=mailto:ruf@example.com; fo=1<\/em><\/p>\n\n\n\n

If you are new to DMARC then you might initially consider setting p=none<\/em>
<\/p>\n\n\n\n

“List Unsubscribe” mandatory from June 1<\/h2>\n\n\n\n

In addition to proper authentication, there are a number of other requirements to consider in order to optimize the delivery rates of your messages. For instance, from June 1st<\/sup>, Gmail will also require a simple, integrated \u201cList Unsubscribe\u201d function<\/a>.

Also ensure your spam complaint rate at Gmail is less than 0.3% at all times<\/strong>. This means a maximum of three complaints per 1,000 emails, a figure that is quickly reached.
You should therefore…<\/p>\n\n\n\n