Free email address services usually have DMARC policies in place that are meant to prevent email scams but can cause delivery issues for legitimate business. And since you don’t own the domain, you do not have control over that domain’s delivery policies. Therefore, at Sender it‘s mandatory to use your own business email address as a sending address to boost deliverability and prevent delivery problems.
For example, if you would use [email protected] as a sender email address, the recipients’ mail server might identify your message as SPAM and move it to the SPAM folder, or reject (bounce) your message completely.
How DMARC Applies to a Sender Identity
When sending email via a service provider such as SENDER, you will be asked to authenticate a domain. All major mail providers such as Google, Microsoft, and others implement DMARC to protect their customers and prevent abuse. Let’s use Google’s Gmail and the email address [email protected] as an example.
Gmail has SPF, DKIM, and DMARC policies. These DNS records include only domains and IP addresses that Google specifically designates as belonging to Gmail.
The Yahoo receiving server will determine that the message was sent using a SENDER IP address and was not signed by Google’s private key. Both SPF and DKIM will fail, causing Yahoo email to employ the DMARC failure policy specified by Google.
Basically, Yahoo, or any other receiving email server, has no way of knowing whether you are using SENDER to send an email for legitimate purposes or spoofing Gmail’s domain.
That’s is why SENDER impose authenticating a domain. The SENDER domain authentication method provides CNAME records that you place on your domain to approve SENDER’S IP addresses, plus will automatically manage your SPF and DKIM records, protecting your domain’s reputation.
Many of the popular email providers implement DMARC, including:
- Microsoft (Hotmail, MSN)
- And many others