Authentication Settings

Authenticating your emails by authorizing our servers to send email on your behalf helps your campaigns to avoid spam filters, and also to prove that your email campaigns are not a forgery.

Authentication is a great way to improve deliverability, confirm that the sending server is legitimate, and also ensures that your email campaigns are reaching the most recipients.

Automatic Email Authentication

By default your email campaigns are authenticated automatically utilizing white label domains and current standard authentication techniques, including DomainKeys, DKIM, SenderID and SPF records.

When publishing campaigns, you can define your own “from” address for example (news@yourcompany.com).

Additionally, certain email clients, such as Outlook and Gmail, require extra sender details in the “from” field, as shown in the example (highlighted in yellow) below:

Verified Domain - Authentication Highlite

Verified Domain - White Label Authentication

Configuring Custom Mail Server Authentication

Business ISP’s and email providers like Gmail, Yahoo Mail, AOL and Hotmail utilize email authentication as an important layer in their spam fighting arsenal.

You can configure your own custom DNS authentication records, and utilize your existing keys with your EmailPublishPro account. By configuring your account as an authenticated sender, your campaigns can instantly bypass certain filters, giving them a much better chance of arriving at the destination inbox.

DomainKeys/DKIM, Sender ID and SPF

ISPs use one, or a combination of these three protocols to check the legitimacy of email sending servers. For the best delivery results, we recommend that you configure your records to support each of these authentication standards.

  • Sender ID
  • DomainKeys/DKIM
  • SPF: A valid SPF record is automatically generated for your campaigns. If you have your own SPF or Sender ID records configured, additional configuration options are available and outlined below.

DNS Records for DomainKeys/DKIM and Sender ID

Upon request, we can generate the two DNS records required to begin authenticating your email campaigns and your private domain. A new TXT record will be provided to you by email for your custom DomainKeys/DKIIM and Sender ID. Your systems administrator will need to add the new TXT records to the DNS records for your private domain name.

Once you’ve added the two new records to your DNS, please let us know and we will monitor the server and verify that the DomainKeys/DKIM authentication is active and working.

If you already have an existing  DomainKey/DKIM, just forward the following information and we will configure your account.

  • Selector
  • Private key
  • Public key

SPF Records

Because we handle all of the bounces from your email campaigns, we already have a valid SPF record configured on our server. Additionally, if you have a SPF or Sender ID record configured on your own server, please add this to your existing records:

include:cmail1.com

For example:

v=spf1 mx a include:_spf.google.com include:cmail1.com ?all

Publishing Campaigns with an Authenticated Domain

Once the domain and records are authenticating, you will then be able to select your private domain name from the dropdown list, when configuring the “from” setting for your next email campaign.

Verified Domain - Custom "From" Dropdown Menu

Verified Domain - Custom "From" Dropdown Menu

Your emails will now have a much better chance of passing through spam filters to reach their destination, and it is less likely that your private domain name can be used fraudulently by others.

More in this Section