SPF(supported) (dedicated subdomain) DKIM(recommended)
This article covers the SPF and DKIM authentication processes for Netcore and how they are managed in Valimail Enforce. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.
Netcore uses a dedicated subdomain setup for DKIM and SPF configuration.
TABLE OF CONTENTS
- Configuring DKIM authentication for your Netcore emails
- Add a Netcore DKIM key in Enforce
- Configuring SPF authentication for your Netcore emails
Configuring DKIM authentication for your Netcore emails
1. You will first need to add a sender domain in Netcore Email API.
2. Once you have added a sender domain in Netcore Email API, the system asks you to configure two TXT records on your domain's DNS settings. The primary objective of adding these records is to authenticate Netcore Email API servers to send your emails.
3. The first TXT record is to verify the ownership of your domain and authenticate your domain to send emails using Netcore Email API. You will need to add the Netcore service to your domain's Configuration in Valimail Enforce.
4. The second TXT record which the system asks to add is primarily for DKIM validation. It is a method to validate the authenticity of the emails. You will need to add the DKIM key in Valimail Enforce.
5. Once you have added these values in your settings, Press the Check DNS Records button to verify.
You can find the instructions to set up DKIM and SPF for Netcore here.
Add a Netcore DKIM key in Enforce
Configuring SPF authentication for your Netcore emails
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.