We're making it easier to get around Constant Contact with a brand new left navigation. Not all accounts have that change yet, so if your navigation looks different from our articles, that's why–but everything from the top can now be found on the left!
Download one of our QuickStart guides! View it on your desktop, print it out, or bookmark it for easy use!
title
html here
item summary
What's New
Want to stay current with the most up-to-date product news and features all in one place? Check out our Release Notes to read about the newest updates and, more importantly, learn how to use them.
Latest Product Updates
label content here
label content here
label content here
label content here
label content here
label content here
Your search returned no results.
Title
snippet here
new or updated
Last Updated date
Legacy Authentication refers to the original way Constant Contact signed mail on behalf of our customers. Constant Contact was an early adopter of authenticating our customers' mail with DKIM. While we signed all of our mail with our main authentication domain (auth.ccsend.com) we wanted to give our customers a chance to select a subdomain that gave them a separate identity/reputation from our shared auth.ccsend.com domain. This subdomain was also used to bring our customers mail into alignment for SenderID which was used mainly by Microsoft/Hotmail domains. Microsoft has now discontinued SenderID verification and the industry has moved towards requiring messages to be DKIM signed with the domain shown in the body of the message (your verified from address). To ensure the best possible delivery for your campaigns when you own your domain, we recommend setting up Self Authentication such as CNAME or DKIM TXT which will meet the current industry standard.
Constant Contact signs all outbound mail with our default authentication regardless of other authentication setup by the customer. Essentially it tells a receiving server that this is an email created by a Constant Contact customer and sent by Constant Contact. Depending on the email client, this authentication address can appear within the message header of one of your email campaigns or appear in DMARC reporting for the sending domain.
