In October 2015, Google announced changes to its DMARC policy, to be effective June 2016. If you use a 'from' address with @gmail.com to send mail from SharpSpring, this change affects you.
Simply put, if you use an "@gmail.com" from address in your emails sent via SharpSpring, this change means that these messages will bounce or go to the recipient's spam folder.
What is DMARC?
Many domain owners broadcast to the world (via DNS) how email claiming to come from them should be handled.
A DMARC policy allows a sender to indicate that their messages are protected by SPF and/or DKIM, and tells a receiver what to do if neither of those authentication methods passes – such as junk or reject the message. DMARC removes guesswork from the receiver’s handling of these failed messages, limiting or eliminating the user’s exposure to potentially fraudulent & harmful messages. DMARC also provides a way for the email receiver to report back to the sender about messages that pass and/or fail DMARC evaluation.
Gmail’s DMARC policy is consistent with many other major email providers, such as Yahoo and AOL, who have had DMARC reject policies for a couple of years now.
What do I need to do?
To help ensure your email gets delivered, we recommend the following:
- Begin using your own domain (e.g. @mycompany.com) as the 'from' address for sending email in SharpSpring, rather than freemail domains such as Yahoo, AOL, or GMail
- Review your existing SharpSpring email templates, including those triggered by automation, and adjust the 'from' address as needed
For more information about this policy change:
- Review the Google announcement from October 2015
- Learn more about efforts to combat fraudulent email from Domain-based Message Authentication, Reporting & Conformance (DMARC)