Email Service Provider DMARC Policy Change: SPAM Preventative Measures
|Knowledge Article Number||000193813|
|Description||*Note: The details below utilize Yahoo.com as an example; however other Email Service Providers including but not limited to AOL.com, have adjusted their policies around DMARC.*
Yahoo.com DMARC Policy Enhancement:
As of April 8, 2014, Yahoo has applied a stricter email validation policy in an attempt to prevent spam and other types of malicious phishing scams. Yahoo's DMARC policy is currently advising email service providers to reject emails from @yahoo.com addresses that do not originate from Yahoo's mail servers. In essence, Yahoo is preventing email service providers who use a @yahoo.com address as the FROM value to send messages to email providers that are DMARC compliant.
What this means for Salesforce.com Users:
Salesforce.com delivers emails with a User defined FROM email address, but the mail originates from Salesforce.com mail servers. If a Salesforce User record is configured to deliver emails with a FROM address of @yahoo.com, and the recipient of the email is DMARC compliant, the email will be rejected. Currently, the Salesforce.com mail infrastructure has no method to circumvent the policy set forth by Yahoo.
Salesforce.com is looking into options to mitigate the policy change.
As there is no workaround available in Salesforce.com due to the restrictions deployed by Yahoo, one option would be to register a domain with mail account services that the organization owns and controls. The newly generated email addresses can be re-registered with the Salesforce User record.
For Organizations that own their domain, options to mitigate: