How to set up DMARC for EmailOctopus in Valimail

Updated over a week ago

This article covers the SPF and DKIM authentication processes for EmailOctopus and how they are managed in Valimail. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.

Configuring DKIM authentication for your EmailOctopus emails

Click Verify domain and enter your domain name.

Once you've clicked verify, you'll be presented with records that you will need to copy across to the service that handles your DNS settings (this is usually where you bought your domain). Create the new DNS records, copying the settings exactly as they appear in EmailOctopus.

Once you have copied all your records across, return to EmailOctopus and click the Complete Verification button at the top right to verify you have added all four records correctly.

Note: You may notice that we generate only CNAME records and no SPF record. That's not a mistake, we take care of the SPF record on our end, you don't have to edit it. We also generate a TXT record to set up your DMARC โ€“ adding this record to your DNS is required for your domain to be fully authenticated as a sender.

NOTE: If you manage you domain in Valimail, you will need to add the CNAME DKIM key on your domain's configuration page in the Valimail platform, and any other record will go in your DNS.

You can also find the instructions on how to set up DKIM and SPF for EmailOctopus, here.

Add an EmailOctopus DKIM key in Valimail

You can find more detailed information on how to add a DKIM key in Valimail, here:

Configuring SPF authentication for your EmailOctopus emails

Once you establish that EmailOctopus is an authorized sender for your domain, you will need to add the service in your Enabled Senders.

You will find more detailed information on how to add a service for your domain in Valimail, here:

Note: We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.

Did this answer your question?