If you send emails using the Email app on Marketing 360®, it is required that you authenticate your sending domain (the domain name that is attached to the email address where you send emails from). This allows receiving mail servers to verify that the emails were authorized by the owner of the domain name, and have not been tampered with.
To authenticate your domain, you will need to make changes within your Marketing 360® Email dashboard and your domain registrar that hosts your sending domain.
First, you will set up a sending domain in your Marketing 360® Email app.
The records you'll need to add in the following steps can be found by clicking on the ellipsis to the right of the domain you're adding under View details.
Note: Each domain registrar has different settings for adding DNS records, so we are unable to provide support on navigating their platform. If you hit any roadblocks, then you can contact your domain registrar's support team, and reference the steps in this article.
You will see a confirmation message once the domain has been successfully authenticated. The next time you create an email campaign, you will be able to select your authenticated domain when defining the sender.
Once you have verified your DKIM setup, the next step is to ensure that your sending domain also has a valid DMARC record.
The domain you're setting up may already have a record beginning with _dmarc. If so, you should probably skip this step. Any valid existing DMARC configuration is acceptable, and making changes to an existing record could have dangerous consequences to your organization's email ecosystem.
You can check that what's there is valid with a tool like EmailStuff validator if you're not certain. As with all technical things, get assistance if needed.
If you do not have a DMARC record, the one we are suggesting is the minimal valid record. It is safe to add without having any adverse impact on any of your organization's mail, and will be useful for establishing the legitimacy of the email you're sending.
_dmarc
into the name field. Some require you to enter the full cm._domainkey.mail.example.com, others only need the cm._domainkey part.v=DMARC1; p=none;
Note: Each domain registrar has different settings for adding DNS records, so we are unable to provide support on navigating their platform. If you hit any roadblocks, then you can contact your domain registrar's support team, and reference the steps in this article.
The final step in the authentication process is to add an SPF record for your sending domain. This is optional, but still a recommended action to provide receiving servers further evidence of the legitimacy of the mail you're sending through our servers.
The process depends on whether you already have an SPF record in place. To determine that, you can use the EmailStuff SPF checker or just look for a record on your sending domain that contains "v=spf1".
These steps assume you are already logged into your DNS host.
If you have an SPF record already:
include:_spf.createsend.com
immediately after the "v=spf1" in the existing record. Make sure you include a space.If you do not have an SPF record:
v=spf1 include:_spf.createsend.com ~all