Authentication is critical to delivery of your emails. It's an important step to verify that you are legitimate non-spamming sender and allow email providers such as AOL and Yahoo that has strict spoofing policy to pass your emails.
There are a few ways to improve your deliverability.
Using DNS editor: SPF and DKIM
To authenticate your domain, you will need to add a record on your domain provider's zone editor or cPanel. You can add the following Sender Policy Framework (SPF) record as a text record: You can refer to this article for more details.
HOST: example.com (your domain)
DATA: v=spf2.0/pra include:wishpond.ne
You can add similar DomainKeys Identified Mail (DKIM) record as a CNAME record. To obtain more information about DKIM record, please contact firstname.lastname@example.org
Domain-based Message Authentication Reporting and Conformance (DMARC)
Every email domain has policies that help decide whether incoming messages should be accepted or rejected. DMARC is one of these policies. It stands for Domain-based Message Authentication, Reporting, and Conformance, and takes effect if an email fails certain types of authentication.
DMARC policies benefit the email community as a whole because they help prevent phishing, spoofing, and the delivery of fraudulent emails. However, strict DMARC policies can sometimes misidentify your legitimate marketing emails as fraudulent and reject them.
To improve deliverability, we encourage you to use a From email address at a domain owned by you or your organization, like email@example.com. Not only will this help avoid delivery issues, it can help your subscribers recognize your brand.
You'll notice when adding your email address on the platform, we recommend an email address type as above.
If you don’t have an email domain to use as the From email address for wishpond campaigns, you can register one.
There are a number of different places where you can register a domain, but we recommend google domains. See a list of options below:
If you encounter a large number of bounces at your domain, or a domain owned by your organization, check your DMARC policy to see if it’s strict or relaxed. It’s possible your DMARC policy is set up to tell receiving servers to reject emails that fail SPF or DKIM authentication.
When you register your own domain, you may be able to avoid certain delivery problems by updating your DMARC policy to tell receiving servers to accept emails sent through other servers on behalf of your domain, even if they fail SPF or DKIM authentication. A relaxed DMARC policy also helps ensure that your subscribers will receive emails like signup or unsubscribe confirmations. The DMARC update process varies by hosting service, so contact your hosting provider or IT department to help set it up.