✅ Email Domain Authentication

Inês Batata

Email sender domain authentication (or simply Domain authentication) is the process that allows you to tell email service providers that Pipedrive is a trusted sender from your domains.

Domain authentication is about security and deliverability, as it helps you protect your brand's reputation and helps your emails successfully reach the inbox.

➡️ Sounds complicated but we make it easy for you with this step-by-step tutorial. Happy campaigning! 

 

🔔 Follow Best Practices to never miss out on new tips. Set your notification preferences. 🔔

Markus Funk

HI, the link to the guide is dead (404)

BaptisteBLC

Oh 🤩

Adios Mailigen

Anton Rutkovskyi_53543

Markus Funk said:

HI, the link to the guide is dead (404)

Just fixed it Markus - could you please try again) 
 

BaptisteBLC

I just did it and it works.

The absence of DKIM will not be a problem?

Anton Rutkovskyi_53543

Baptiste said:

I just did it and it works.

The absence of DKIM will not be a problem?

HI Baptiste! 
The two CNAME records are for DKIM, so once adding them to your DNS records along with TXT (company identifier), the domain will be authenticated and outgoing email messages will be signed with the DKIM ))

Marcus Belke

... and it works great! Thanks, well done. 

Stephen Dorling_4110

We're trialling Campaigns and our Marketing Manager is really impressed with the design capability.  We're only a small business and ideally would like to keep everything in Pipedrive for simplicity.

Currently, we use Outfunnel to sync data between Pipedrive and Mailchimp.

However, we've come into a problem.  We have our DMARC record set to Reject and in testing the Campaigns module it sends with a default reply-to address that's different to the sending address/domain.

e.g. we send out as info@companydomain.com but the reply address is 'text@pd1.onpdr.com'

We use OnDmarc to manage our DMARC record (just as Pipedrive does for it's own DMARC records management) so we manage sending sources for SPF/DKIM in that.  

Is there a way to change/manage the reply-to address for Campaigns or are there plans to enable that in the future? - It's the only way I believe we'll then be able to pass DMARC checks and use Campaigns.

Aleksandrs Vilums

Stephen Dorling said:

We're trialling Campaigns and our Marketing Manager is really impressed with the design capability.  We're only a small business and ideally would like to keep everything in Pipedrive for simplicity.

Currently, we use Outfunnel to sync data between Pipedrive and Mailchimp.

However, we've come into a problem.  We have our DMARC record set to Reject and in testing the Campaigns module it sends with a default reply-to address that's different to the sending address/domain.

e.g. we send out as info@companydomain.com but the reply address is 'text@pd1.onpdr.com'

We use OnDmarc to manage our DMARC record (just as Pipedrive does for it's own DMARC records management) so we manage sending sources for SPF/DKIM in that.  

Is there a way to change/manage the reply-to address for Campaigns or are there plans to enable that in the future? - It's the only way I believe we'll then be able to pass DMARC checks and use Campaigns.

Hi Stephen

Is there still an issue?

When you send out email campaigns from an authenticated domain, reply-to email will be sender email or email that you add in reply-to field. 

And when you send out email campaigns from an authenticated domain, DKIM always will be PASS (you should see it in your OnDmarc tool). SPF cannot be passed with your domain since our sender pd1.onpdrc.com is the main sender with warmed inbox delivery IP addresses. 
To be successful with DMARC, only need to pass one - DKIM or SPF. With domain authentication you can get pass DKIM. 

Let me know for any additional questions.

Best,

Aleksandrs

Dana_V

Hello,

Is it possible to authenticate my email sender domain in automations? Or is this option only available in Campaigns?

Thank you!