search
Sender Authentication and Connected Email Scenarios

Last Updated:

1 - No Sender Authentication and No Connected Email - Direct Message

  • Without sender authentication or connected email, you have a much higher chance that the message will land in a contact’s Spam or Promotions folder.
  • You can see the mailed-by and signed-by are “off-brand”.

1.png

  • Below you can see what the contact see’s when they reply to the direct message.

2.png

  • Here you can see the response on the contact timeline:

4.png


2 - No Sender Authentication/No Connected Email - Campaign

  • Without sender authentication or connected email, you have a much higher chance that the campaign message will get sent to a contact’s Spam or Promotions folder.
  • You can see the mailed-by and signed-by are “off-brand”.

5.png

  • Below you can see what the contact sees when they reply.

6.png

  • Below you can see the response in the contact’s timeline in Beamery.

7.png

  • The SendGrid generated thread “pdhsviub9” is used to enable Beamery to track campaign statistics.

8.png
3 - Sender Authentication/No Connected Email - Direct Message

  • Sender Authentication will drastically increase the deliverability of the messages sent from Beamery.
  • Below you can see the mailed-by (subdomain) and signed-by (domain) are on brand (beamery.tech).

9.png

  • Below you can see what the contact sees when replying to the message.

10.png

  • Below you can see the response from the contact in the contact’s timeline.

11.png

4 - Sender Authentication/No Connected Email - Campaign

  • Sender Authentication will drastically increase the deliverability of the messages sent from Beamery.
  • Below you can see the mailed-by (subdomain) and signed-by (domain) are on brand (joseph.beamery.tech).

12.png

 

  • Below you can see what the contact sees when replying to the campaign message.

13.png

  • Below you can see the response in the contact’s timeline.

14.png

  • The SendGrid generated thread “defvjk_rc” is used to enable Beamery to track campaign statistics.

15.png

 


5 - No Sender Authentication/Connected Email - Direct Message

  • Below you can see there is no subdomain or corresponding SendGrid thread ID.
  • The direct message you sent via Beamery will show up in the sender’s “Sent” folder.
  • Nylas API is being used.

16.png

 

  • Below you can see what the contact sees when replying to the direct message. You will notice they only see the actual email address.

17.png

  • Below you can see the contact response on the contact timeline in Beamery.
  • You will also see the contact’s response in your actual email inbox.

18.png

19.png

6 - No Sender Authentication/Connected Email - Campaign

  • Below you can see the “from” address is the actual email address, but because there is no sender authentication you will see the “via sandbox.beamery.com/” domain.

20.png

  • Below you can see what the contact sees when replying to the campaign message.

21.png

  • Below you can see the contact response on the contact timeline

22.png

  • Below you can see that even though the response is processed via connected email and synchronised via the Nylas API, the campaign statistics are still tracked. 

23.png


7 - Sender Authentication/Connected Email - Direct Message

  • Below you can see that the “From” email address is the actual email address and the message was mailed-by and signed-by the actual email server.

24.png

  • Below you can see what the contact sees when replying to the direct message.

25.png

  • Below you can see the response from the contact has been synced to the client’s inbox and the contact’s timeline in Beamery.
    26.png27.png

8 - Sender Authentication/Connected Email - Campaign

  • Sender Authentication will drastically increase the deliverability of the messages sent from Beamery.
  • Below you can see the mailed-by (subdomain) and signed-by (domain) are on brand (joseph.beamery.tech).


28.png

  • Below you can see what the contact sees when replying to the campaign message.
    29.png
  • Below you can see the response from the contact has been synced to the client’s inbox and the contact’s timeline in Beamery.
    30.png

31.png

  • Below you can see that even though the response is processed via connected email and synchronized via the Nylas API, the campaign statistics are still tracked. 

32.png


9 - Sender Authentication Secondary Email Domain - Direct Message

  • Sender Authentication will drastically increase the deliverability of the messages sent from Beamery.
  • Below you can see the mailed-by (subdomain) and signed-by (domain) are the secondary email subdomain (joseph2.beamery.tech).
  • Below you can see in the reply-to section that the SendGrid link leverages the primary email subdomain (talent.joseph.beamery.tech).
    • Note: Beamery will use the first domain added for inbound parsing. This is why you are seeing “joseph-roth-5qwn5fad9@talent.joseph.beamery.tech” as part of the reply-to header in the email. 

33.png

  • Below you can see what the contact sees when replying to the message

34.png


10 -Sender Authentication Secondary Email Domain - Campaign

  • Sender Authentication will drastically increase the deliverability of the messages sent from Beamery.
  • Below you can see the mailed-by (subdomain) and signed-by (domain) are the secondary email subdomain (joseph2.beamery.tech).
    • Note: Beamery will use the first domain added for inbound parsing. This is why you are seeing “joseph-roth-e22d5zkhc@talent.joseph.beamery.tech” as part of the reply-to header in the email. 

35.png

  • Below you can see what the contact sees when replying to the campaign message. They see the SendGrid address which is used for tracking campaign statistics and the joseph2.beamery.tech email address as that is the address the user sent the campaign from. 

36.png

  • Below you can see the response from the contact has been synced to the client’s inbox and the contact’s timeline in Beamery.

37.png

  • Below you can see that the statistics on the campaign are recorded as expected. The campaign statistics are being tracked using the ‘joseph-roth-e22d5zkhc@talent.joseph.beamery.tech’ address since Beamery will always use the first domain configured for inbound parsing.

38.png

11 - Sender Authentication - Client is unable to use their primary email domain

Issue: Clients are sometimes unable to get permission from their IT or Information Security team for Beamery to send emails on behalf of their primary email domain. The client is unable to provide us with an actual email address that we can use for sender authentication. However we still need to ensure that the messages coming out of Beamery are authenticated and have a high deliverability score in order to get into a contact’s inbox. We also need to ensure that the responses get back into Beamery.

Solution: Beamery can provide a solution to this by using backend mapping in SendGrid as long as the client can provide a legitimate DNS that we can generate CNAME credentials for.

Assumptions: For the steps below we will assume we are helping a company “Worldwide IT” whose primary email domain is “worldwideIT.com”, but Beamery is unable to send messages on behalf of the primary domain.

  • Step 1: The client must procure a legitimate DNS.
    • Ex: careers-worldwideIT.com
  • Step 2: The client must decide on a subdomain for the primary domain.
    • Ex: talent.careers-worldwideIT.com
  • Step 3: Beamery will generate CNAME credentials and provide them to the client.
  • Step 4: The client will configure the CNAME credentials on their DNS for the subdomain.
  • Step 5: The Beamery IC will submit a Jira ticket to team Aether to request two mappings in SendGrid (See sample Jira ticket logged for AAH).
    • SendGrid Reply-To Mapping Details
    • SendGrid Failed Email Forwarding Mapping Details
    • Note: More detail to be added here soon on how the backend mapping solves our issues.
  • Step 6: Users must be setup with an email address in the format, “user@talent.careers-worldwideIT.com”
    • Note: The value for “user” must match the actual primary email as the mapping done in Step 5 will simply swap out the domain.
      • Ex: If the actual email address is “Jake.Smith@worldwideIT.com”, then the email they are sending from in Beamery must be “Jake.Smith@talent.careers-worldwideIT.com”. They must select this email when sending direct messages to contacts. It is also best practice for users who are expected to send campaigns to have a more generic email with the same domain (Example: “WorldwideITCampaigns@talent.careers-worldwideIT.com”).

Result: The client will be able to send authenticated emails from Beamery with a high chance of deliverability. They can also be assured that responses will get back into Beamery and in their primary work email as they would if we were able to leverage their primary email domain.