Skip to main content
Prowly

How to set up DMARC for Prowly in Valimail

Updated over a week ago
SPF(not supported)
DKIM(recommended)

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

1. Start by clicking the gear icon in the top-right corner and click on Email setup.

2. When you get there, click the Manage domains button in the Domain authentication section. Then, click Authenticate domain.

3. Enter the domain you want to authenticate. This should be a domain you're going to use in your emails as the sender address (also known as the From field).

4. Copy all DNS Records into your domain provider admin panel.

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.

5. Once all the records are added properly, click Verify configuration. Keep in mind that DNS changes may take up to 48 hours to propagate, so it can take time to verify your domain. We will send you an email with confirmation when the setup is done.

6. That’s it! When your domain is authenticated, you should see a screen like the one below. At least the first four records should be highlighted in green.

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

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

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