Communicator. Branded Sending Domain July Branded Sending Domain

Size: px

Start display at page:

Download "Communicator. Branded Sending Domain July Branded Sending Domain"

Camron Walters
6 years ago
Views:

1 Branded Sending Domain Communicator Branded Sending Domain July 2017 Version 2.1 This document includes instructions on how to set up a new sender domain and ensure this is configured correctly.

2 Contents Contents Mail Exchange Record Information Sender Policy Framework Record Address Record Information Domain Keys/DKIM Record Information DMARC Record Information Branded Sending Domain Page 2 of 8

3 This document details the records that will need to be configured for your domain to work with Communicator. It is essential that all records are added to ensure deliverability. You cannot use a domain that is already being used for internal mailing or other activities. This is because all s sent to your internal addresses will be sent to Communicator and not to your servers. We recommend that your Branded Sending Domain is a subdomain of the sender, for example .yoursite.com. The Branded Sending Domain should not identify a company other than the sender (this is a requirement of eprivacy) and should not be a new domain which only appears to be related to the sender, for example yoursiteoffers.com (this is a deliverability requirement to prevent s being classified as phishing scams and rejected or sent to the junk folder). Existing configurations that do not adhere to this standard should be updated at the earliest opportunity. Branded Sending Domain Page 3 of 8

4 Mail Exchange Record Information The MX record specifies where a mail server should send for a specific domain. For example, Every time an is sent, it is forwarded to your domain and the MX record on the domain points the message to the exact delivery location. In order for Communicator to handle non-immediate bounces and replies for dispatches sent via Communicator, the MX record for the branded sending domain Create two MX records for <sending domain> both with equal weightings of 10. The first: mail1.communicator .com Weighting: 10 The second: mail2.communicator .com Weighting: 10 Branded Sending Domain Page 4 of 8

5 Sender Policy Framework Record The Sender Policy Framework (SPF) Record is used to confirm that Communicator from your organisation. son or ISPs/IEPs monitor sends, and will see that Communicator is sending out from a domain which is not their own. They will then check the SPF record of the domain that Communicator is sending out on behalf of. As long as this is pointing back to Communicator, messages will be authenticated. Without this, they will assume we do not have consent, and will block most, if not all messages. Create 2 TXT records as follows: The first: v=spf1 include:spf.communicator .com -all The second: spf2.0/pra include:senderid.communicator .com -all Branded Sending Domain Page 5 of 8

6 Address Record Information An A record sets the IP address or alias of a domain. When you search for for example in your web browser, the A record on that domain directs you to the correct website. Setting the A record allows for links in s to display and then render on your preferred domain rather than communicator .com. For example, without a branded sending domain, the recipient would view links as: With a Branded Sending Domain the recipient would view links as: This improves recipient trust in your s and reduces the risk from phishing filters. Please create an A record for <sending domain> that points to the below IP address Branded Sending Domain Page 6 of 8

7 Domain Keys/DKIM Record Information Domain Keys and DKIM have the same purpose as the SPF Record. as an additional check of authenticity. Again, they check for these records to verify that we have your permission to send using this domain. If they do not see these records, they will assume we do not have permission and again will not let your s reach the recipients. A subdomain _domainkey.<sending domain> needs to be created as a TXT record: _domainkey.<sending domain> o=-; r=domainkeys@communicatorcorp.com An additional TXT record also needs to be created: k1._domainkey.<sending domain> k=rsa; p=migfma0gcsqgsib3dqebaquaa4gnadcbiqkbgqc5tncg7wh5e3toz3iutacfpxdedvdbn46 GvY5pnObKZwcLmgEkLQHqZMbWSoCqo5qGUaUzUADUw7g1qCGccNbDftNjotwNrHDqYIRwYKZD uo8httis6tujl+4jhb3gl6pnpdp3p2trjfyypgk3jmybcvrudfc2fdubtw2yczxntqidaqab Please ensure that any line breaks are removed when entering the text value. Branded Sending Domain Page 7 of 8

8 DMARC Record Information DMARC is an additional and relatively new authentication technology. DMARC helps receivers avoid false positives with transient failures in either DKIM or SPF, because DMARC only fails if both fail. Create a TXT record as follows: _dmarc.<sending domain> v=dmarc1; p=quarantine; rua=mailto:dmarc@communicatorcorp.com; rf=afrf; Branded Sending Domain Page 8 of 8

Automatic Delivery Setup Guide

Automatic Delivery Setup Guide for GuideSpark Communicate Cloud Table of Contents Summary: Working with Automatic Email Delivery... 1 What your IT department needs to know... 2 Prerequisite: Select a Targeted Audience... 3 Enable Automatic