How to Set Up DKIM for your Sender Domain
You may need to set up DKIM for your sender domain to improve deliverability or you are experiencing email spoofing issues.
Adding a Sender Domain and setting up DKIM will help assure your subscribers that emails MailPoet sends on your behalf were indeed sent by you and thus may improve the deliverability of your emails.
If you have a DMARC policy set up for your sender domain with "p=quarantine" or "p=reject" policy and you are using our MailPoet Sending Service, you need to add DKIM to your sender domain.
Reference: How To Fix Email Violates Sender Domain's DMARC Policy Error
You will need to add the three DNS records through your DNS provider. Usually, it is the same organization you purchased your domain from (e.g. GoDaddy, NameCheap), or your hosting company.
And you're done! Now you can continue sending emails as normal and enjoy the improved deliverability!
If you've added the records, but are having trouble verifying them:
- Check if your records are propagated properly and have the correct values in pubic DNS. To do that, visit these links (change example.com to your sender domain first):
- Please double check that the record types, names are values in your DNS manager exactly match the values requested in MailPoet interface;
- If you've just added the records, try waiting for 5-10 minutes and click "Verify DNS records" again. DNS changes can take up to 24 hours to propagate, but commonly you may see them within 5-30 minutes;
- Double check the DNS record name. Some DNS providers may create DNS records with a duplicate the domain name, causing "mailpoet1._domainkey.example.com" record to be incorrectly created as "mailpoet1._domainkey.example.com.example.com".
If this occurred in your case, try removing the domain name from the record's name, leaving it as " mailpoet1._domainkey", "mailpoet2._domainkey" and "_mailpoet".
- If you use Cloudflare as your domain's DNS provider, the Proxy Status should be changed from "Proxied" to "DNS only" for both of the CNAME records:
- Also in Cloudflare, make sure that CNAME Flattening is turned off, as it can cause issues with verifying the records: https://developers.cloudflare.com/dns/additional-options/cname-flattening/