✅ Email Domain Authentication

Inês Batata
Inês Batata Admin Posts: 3,155 COMMUNITY MANAGER
2500 Comments Second Anniversary 5 Likes First Answer
edited July 25 in Workflow Automation #1
image

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. 🔔

Screenshot%202022-01-17%20at%2016.48.40.png?1642438272588

Comments

  • Markus Funk
    Markus Funk Posts: 120
    100 Comments Second Anniversary Name Dropper Photogenic
    edited March 10 #2

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

  • BaptisteBCA
    BaptisteBCA Community Driver Posts: 249
    100 Comments Second Anniversary Name Dropper Photogenic
    edited March 10 #3

    Oh 🤩

    Adios Mailigen

  • Anton Rutkovskyi_53543
    Anton Rutkovskyi_53543 Posts: 7 PIPEDRIVE PRODUCT MANAGER
    Name Dropper First Comment First Anniversary Photogenic
    edited March 10 #4

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

    Just fixed it Markus - could you please try again) 
     

  • BaptisteBCA
    BaptisteBCA Community Driver Posts: 249
    100 Comments Second Anniversary Name Dropper Photogenic
    edited March 10 #5

    I just did it and it works.

    The absence of DKIM will not be a problem?

  • Anton Rutkovskyi_53543
    Anton Rutkovskyi_53543 Posts: 7 PIPEDRIVE PRODUCT MANAGER
    Name Dropper First Comment First Anniversary Photogenic
    edited March 10 #6
    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
    Marcus Belke Posts: 16
    edited March 16 #7

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

  • Stephen Dorling_4110
    edited March 16 #8

    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 [email protected] but the reply address is '[email protected]'

    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
    Aleksandrs Vilums Ex-Pipedrivers Posts: 22 PIPEDRIVE PRODUCT MANAGER
    Photogenic First Anniversary Pipedrive Employee
    edited March 16 #9

    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 [email protected] but the reply address is '[email protected]'

    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