Skip to main content
Peoplevine

How to set up DMARC for Peoplevine in Valimail

Updated over 5 months ago
SPF(supported) (dedicated subdomain)
DKIM(recommended)

This article covers the SPF and DKIM authentication processes for Peoplevine and how they are managed in Valimail. Because this service leverages Sendgrid's email infrastructure, it requires additions to your DNS records outside of the Valimail platform. Adding Peoplevine as an authorized sender in the Valimail platform usually requires a dedicated subdomain to be pointed to the Sendgrid infrastructure and typically the DKIM keys will be added in the Valimail platform.

Configuring DKIM authentication for your Peoplevine emails

Setting up a Domain Key (DKIM) you further identify your e-mails that they came securely from your server. In your DNS, we recommend you setup the following DNS entries:

CNAME - Host: sender - VALUE: sender.peoplevine.net

CNAME - Host: s1._domainkey - VALUE: s1._domainkey.peoplevine.net

CNAME - Host: s2._domainkey - VALUE: s2._domainkey.peoplevine.net

Important: If you manage DKIM for your domain in Valimail, you will need to add the 2 CNAME DKIM keys (s1, and s2) on your domain's Configuration page in Valimail Enforce and the 3rd CNAME record in your DNS.

Once you have this in place, please send a request to [email protected] to setup your DKIM. Simply provide us with the email address your emails are being sent from.

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

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

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