WBP Guide: How to prepare for Google & Yahoo's new sender requirement
In recent updates, both Google and Yahoo have introduced new sender requirements that will impact all senders, especially those who send over 5,000 emails a day. It is essential for email marketers and businesses to understand these changes and take necessary steps to comply with the new standards. Failure to meet these requirements can result in emails being delayed, blocked, or marked as spam, leading to a decrease in email deliverability.
To help you navigate these updates effectively, Google and Yahoo have provided detailed guidance and insights in their official articles regarding the new sender requirements. These resources offer comprehensive information that will assist you in understanding and implementing the necessary changes.
Changes in the Sender Requirements
Several changes have been introduced in the new sender requirements that will affect various aspects of email sending. Let's take a closer look at each of these changes:
1. Email Compose Slider/Bulk Email Slider
The signed-up email address from the 'from' drop-down will be disabled if the domain is not verified or if the user has not connected Gmail.
2. Add Email/Add Email Reminder in Sales Sequence Flow
The user's email will be disabled from the dropdown, and by default, the Freshsales domain will be selected in the 'from' address.
3. Connected Gmail Mailbox Limit
If the user has connected their Gmail mailbox and exceeds the email sending limits, only if the domain is whitelisted, it will automatically fallback to the Freshsales email domain.
4. Sales Sequences and Scheduled Emails
If users continue to use an unverified email domain, the changes will impact these emails being sent.
5. Workflows and Team Inbox
The ‘Record Owner’ selection for the "from" address will be disabled. Domain verification will be needed to send emails using the team inbox as well. Email domains in the 'from' address for domains that are not verified will be disabled.
6. Email Settings
The email limit per domain is 5,000. Domains that are not verified or domains where the mailbox is not connected will be disabled in the 'from' address.
Steps to Avoid Disruptions
To avoid any disruptions in email deliverability and comply with the new sender requirements, it is crucial to take the following steps:
1. Verify Your Domain
Domain verification is a necessary step to ensure that your emails are sent securely. There are two ways to verify your domain:
Verify Domain Manually:
You can manually verify all senders by adding the DNS records of your domain to your DNS Manager. This can be done by the Admin.
Connect Gmail Inbox:
Connecting your Gmail inbox automatically verifies the Google sender. However, it only verifies individual email addresses. Each team member must connect their inbox individually to ensure their addresses are verified.
2. Keep Spam Complaints Low
Keeping your spam complaints at a minimum is crucial to maintaining good email deliverability. To achieve this, consider using tools like Postmaster to gain insights into your email deliverability rate, spam rates, and other relevant information.
3. Unsubscribe Option
Adding a one-click unsubscribe option in your emails allows recipients to easily and immediately opt-out. This is essential to comply with the new email standards and ensure a positive user experience.
DMARC Record Configuration Options
When setting up your DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy, you have two main options to choose from:
Option 1: Implement a p=none DMARC Record
Description:
Create a DMARC record with a policy of "none" (e.g., "v=DMARC1; p=none"). Include a rua tag to specify an email address for receiving aggregated DMARC reports.
Impact:
This option instructs Gmail and Yahoo to deliver your emails even if they fail SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) checks. Although it safeguards your email sending, it does not prevent potentially harmful emails that spoof your address from being delivered.
Advantage:
You can track unauthorised email activity using DMARC reports.
Example DMARC Record: "v=DMARC1; p=none; rua=mailto:yourreport@email.com"
Option 2: Implement a p=quarantine or p=reject DMARC Record
Important: Before setting up a "quarantine" or "reject" policy, verify that your domain is properly authenticated.
Description:
Choose a stricter enforcement policy with "quarantine" (emails are marked as spam) or "reject" (emails are not delivered at all).
Impact:
Quarantine Policy:
Emails may be sent directly to the spam folder, undergo temporary quarantine, or face stringent anti-spam checks.
Reject Policy:
Emails that fail SPF and DKIM checks are not delivered.
Example DMARC Records: Quarantine: "v=DMARC1; p=quarantine" Reject: "v=DMARC1; p=reject"
For detailed guidance on setting up a DMARC record on your domain, you can refer to our comprehensive KB article or consult external resources. Additionally, if you need assistance with adding DNS records, specific instructions are available from providers like GoDaddy, Namecheap, Microsoft Azure, AWS, and Cloudflare.
By following these steps and implementing the necessary changes, you can ensure high deliverability and compliance with the new email sending standards set by Google and Yahoo. It's essential to stay updated with any further changes and adapt your email practices accordingly to maintain a successful email marketing strategy.
If you need further guidance with email marketing or want to utilise our email marketing service, contact our web development team in Manchester today.
