How do I set up Elastic Email so its email passes DMARC?

What does Elastic Email ask me to publish?

This article applies to sender domains in Email Marketing and Email API.

Elastic Email prints these values in its own documentation, the same for every customer.

Elastic Email makes the other values for your account, so we do not print them here.

include:_spf.elasticemail.com

api.elasticemail.com

Where in Elastic Email are my values shown?

In order to verify your domain, navigate to Settings>Domains>Manage Domains screen

In Elastic Email, go to Settings, then Domains, then Manage Domains. The DKIM record is shown in the domain's details.

Copy each value from there exactly as shown, and add each record at your DNS host.

How do I add Elastic Email to the SPF record I already have?

SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS. If this limit is exceeded, the implementation MUST return "permerror".

Add include:_spf.elasticemail.com inside the one SPF record you have, before its last word, and keep every service already in it. Never add a second SPF record: two make the check fail for every message.

Will p=reject block Elastic Email email?

SPF and DKIM are prerequisites of DMARC and must be in place before setting up a DMARC policy.

Not once Elastic Email signs your email with your domain's DKIM key. DMARC passes when a message passes DKIM or SPF for your own domain, and the DKIM records Elastic Email gives you are on your domain.

Elastic Email says SPF and DKIM must be in place before you set a DMARC policy.

Before you raise your policy, read your DMARC reports and check that email from Elastic Email passes.