How to set up DMARC for Veeva in Valimail

Updated over a week ago
SPF(supported) / (dedicated subdomain)

This article covers the SPF and DKIM authentication processes for Veeva 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 Veeva emails

1. Create a CRM Support Ticket to Veeva in order to create the domain/s in the enterprise email engine.

2. Create the specific DNS entries provided by CRM Support to authorize the domain. Three DNS records are required per domain:

  • One TXT record for SPF and SenderID authentication

  • One TXT record for DKIM and DomainKeys authentication. A DKIM DNS record is required to prevent customer emails from being placed in the Spam folder

  • One CNAME record used for URL redirects. This is used to track recipient opens and click-throughs

3. Add the TXT DKIM key on your domain's Configuration page in Valimail Enforce. The other TXT and the CNAME record need to be added to your DNS.

4. CRM Support validates the customer supplied DNS entries, either with a standard dig (on Unix) or nslookup (on Windows). For example:


dig TXT

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

Add a Veeva 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 Veeva emails

Once you establish that Veeva 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?