Note: this article applies to Marketing App users for all editions (Marketing Cloud Next Growth/Advanced, Salesforce Starter, Salesforce Pro Suite, and Salesforce Foundations).
Beginning February 2024, bulk mail senders must meet new guidelines regarding message authentication, unsubscription flows, and spam rates. Failure to meet these guidelines can result in an IP or IP range being blocked or rejected. Anyone sending 5,000 or more messages a day is considered a bulk sender.
These guidelines are based on the joint statements released by Gmail and Yahoo in October 2023. They’re based on long-standing best practices in email marketing and ensure the protection of the message recipient.
To protect end users, emails must be properly signed and authenticated. Emails must meet these authentication standards: Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain Message Authentication Reporting & Conformation (DMARC).
To meet this expectation, set up authenticated domain for sending email in Marketing Cloud Next (this is a requirement before emails can be sent). More information on email authentication can be found here. To verify that your domain is properly authenticated, you can use a third-party site, such as aboutmy.email, mail-tester.com, or mailgenius.com.
All promotional emails must offer a one-click unsubscribe workflow. Additionally, you must process all unsubscribe requests within 2 days.
All Marketing Cloud Next emails with a promotional classification contain a list-unsubscribe header, which provides a one-click unsubscribe option for the recipient server and helps fulfill this requirement.
As a bulk sender, keep your effective spam rate at or below 0.3%. To help meet this requirement, consider these steps.
For more guidance on deliverability best practices, see Email Deliverability and Email Deliverability Concepts (Trailhead).
004576432

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.