How to set up DMARC for ChargeDesk in Valimail

Updated over a week ago

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

To setup DKIM for your ChargeDesk emails, you can find these records by going to Setup -> Emails and clicking the "Generate SPF & DKIM Records" button.

The DKIM record can also be added by editing your domain's DNS settings to add a TXT record. The TXT record will be unique for your domain and can be generate by clicking the generate button as described above.

NOTE: If you manage you domain in Valimail, you will need to add the DKIM key/s on your domain's configuration page in the Valimail platform.

Verify Records

Once you have added your SPF and DKIM records, you need to click the "Verify Records" button shown below them on ChargeDesk. Until we are able to verify the records, we will not be able to switch over to using them. Due to DNS propagation, we may not be able to immediately verify updates to your DNS records. If this is the case, please wait a few minutes and try again. If this still does not resolve the problem, please contact support for further assistance.

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

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

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