Configuring your domain with DKIM & SPF Records enables the use of a custom From Email address in Alchemer Email Actions and Email Campaigns.
If you prefer to send via a SMTP server, visit the instructions here.
There are two DNS-based records that need to be in place (though both records are of the same type (txt), two separate records are needed):
- SPF record
- DKIM record
The setup process involves configuration both within Alchemer and on the domain's DNS record.
In order to configure your DKIM and SPF records, you will need to be an Alchemer Account Administrator. You will also likely need access to your organization's (or client's) domain administrator or IT Team (or direct access to your domain's DNS record settings).
Alchemer-Side Configuration
At this time Alchemer supports SPF/DKIM setups with a domain only (www.example.com) and does not support subdomain (email.example.com) builds.
To begin your DKIM/SPF configuration within Alchemer, follow these steps:
- Navigate to your account integrations page via Integrations > Data connectors on the left hand navigation menu.
- Scroll to the bottom-half of the Integrations page and click the Configure button next to the Custom Email Settings option.
- Provide an Integration Name. This is the internal title that will be used to identify this integration in Email Actions and Email Campaigns. It is important to make this name something meaningful like DKIM & SPF for alchemer.com.
- (Optional) Determine whether you want this integration to serve as the default for any Email Actions and Email Campaigns that are created going forward.
The option to Use this integration as the default for all new email invitations and email actions will be automatically selected. Un-check the option if needed. - Select Send emails using Alchemer's servers (Setup SPF and DKIM). This will expose additional fields for configuring this integration.
- Within the From Address section, provide your Domain Name and Default From Address.This is the domain that you want to use as your From Address within Email Actions and Email Campaigns. The above Default From Address can be updated when configuring your Email Actions or Campaigns (the domain cannot be updated).
The next several steps will need to be executed within the domain's DNS settings by referencing the SPF Settings section.
Domain-Side Configuration
- Within Alchemer, the SPF Settings section provides users with the SPF Entry that will need to be added to the domain's SPF record. Copy the SPF Entry from the provided field in the custom email integration being created:
Within your domain's DNS settings, create a new TXT record and add the above content. - Back in Alchemer, under DKIM Settings you will need to generate your public key. This public key will then need to be added to your domain's DNS Server.
Click Generate DKIM to generate your public key.
A DNS Domain Name (the DNS domain name for the public key) as well as the DNS Public Key will be generated:
Within your domain's DNS settings, create a new TXT record with the following Name and Content:- Name:
surveygizmokey1._domainkey - Content: paste the DNS Public Key you just generatedImportant! Some systems require that you enter the quotes (that surround the key) and separate the public key into multiple strings under 255 characters whereas other systems for managing DNS do this automatically. This can cause extra quotes to be added to your key and make the DKIM record invalid. If your record is invalid, make sure that there are not multiple sets of quotes surrounding the key wherever it was entered.
- Name:
- Back in Alchemer, click the Save button to finish setup.
You will notice that both your SPF and DKIM Settings are not validated during setup. We will attempt to validate your settings when you Save your integration. We perform this validation by sending a test email (to one of our servers) and reviewing the email headers of that test email.
Your DKIM & SPF Records will need to be verified before you can start using them in email sends. On the main Integrations page, look for the green check-mark under the Verified column.
Within your domain's DNS settings, create a new TXT record and add the above content.
A DNS Domain Name (the DNS domain name for the public key) as well as the DNS Public Key will be generated:
Within your domain's DNS settings, create a new TXT record with the following Name and Content:
The Test Link via email campaigns does not use DKIM/SPF information, and will always come from Alchemer. To test DKIM/SPF, send a live email campaign to the email of choice.
Testing Your DKIM Record
When a new DNS record is created, it can take some time to propagate and be available for querying. Alchemer recommends waiting a few hours following the record being populated before testing. Users may need to wait up to 72 hours for the records to propagate.
an MX record should be set up prior to attempting to enable DKIM/SPF. Some mail clients may reject emails from domains without an MX Record.
To test for a DKIM record, follow these steps:
- Via your browser, navigate to https://mxtoolbox.com/TXTLookup.aspx.
- In the Domain Name field, enter the domain that you want to test and click the TXT Lookup button.
- To see a successful record, enter dkimsgizmo1._domainkey.alchemer.com and click TXT Lookup. This will show you a return for a correctly configured DKIM record.
- Next, enter your domain, for example:
surveygizmokey1._domainkey.yourdomain.comand click TXT Lookup to test your domain.
You can also perform an SPF and DKIM check using https://www.mail-tester.com/spf-dkim-check.
- To see a successful record, enter
alchemer.comin the domain name field andsurveygizmokey1._domainkeyin the DKIM Selector field. - Specifically, with regard to the DKIM Check, a successful record will return "Key Length" information. If a key length value cannot be retrieved, you will see, "We were not able to retrieve the key length..." message. Make sure the key was entered correctly and retry.
Additionally, another resource for performing an SPF record check is DMARC Analyzer.
- DMARC enables customers to confirm the SPF record inheritance tree DNS lookup limit of 10 is not exceeded.
Using "Send Test" with Email Campaigns in Alchemer does NOT use SMTP/DKIM/SPF settings, and will send from Alchemer's Servers (@surveygizmo.com).
Next Steps
Now that you have configured your SPF & DKIM records, learn about customizing your email From Address to use what you have configured:
FAQs
Why did Alchemer implement SMTP and DKIM/SPF?
Most Email Service Providers (ESPs) i.e Mailchimp, Mailgun, and Sendgrid require setting up either an SMTP integration or custom DKIM/SPF records in order to send from a custom 'from address'.
By providing these options to our customers, we are following an industry-standard in order to help increase email deliverability. By using either SMTP or DKIM/SPF to send email, you are decreasing the likelihood of your emails getting caught up in SPAM filters - while also avoiding 'Email Spoofing'.
Do I need to use SMTP or DKIM/SPF to send email from Alchemer?
Only if you need to customize your from address. If you don't need to customize your email from address, you can continue to send Email Actions and Email Campaigns using the default noreply@alchemer.com address.
Can I set up multiple Custom Email integrations, is there a limit?
You certainly can add multiple Custom Email Integrations. We do not currently have a limit in place for the number of Custom Email Integrations that you can add.
What port should I use for SMTP?
Alchemer supports ports 25, 465*, and 587. We recommend using port 587 with TLS enabled to ensure that emails are encrypted during transmission.
Often Email Service Providers (ESPs) work with specific ports and may communicate that with you. We have confirmed that the following ports work with the provided SMTP Hosts:
| SMTP Host** | Port |
|---|---|
| smtp.office365.com | 25 |
| smtp.mandrillapp.com | 587 |
| smtp.sendgrid.net | 587 |
| smtp.mailgun.org | 25 |
*While this port is supported it is technically deprecated for secure SMTP and is only available for backwards compatibility with older systems. If you use 465 they double check that your server supports starttls.
**If you find that one of the above SMTP Hosts (or another one altogether) works with additional ports, please let us know and we will add it to the above list!
Learn more about these options from a June, 2016 Sparkpost article.
Can I use my SMTP or DKIM/SPF integration when emailing Reports or Exports?
The Custom Email Integration is currently available for Send Email Actions and Email Campaigns only.
Can I use both SMTP and DKIM/SPF Integrations at the same time?
While you can create separate SMTP and DKIM/SPF integrations for your Alchemer account, you can only use one or the other for any given email action or email campaign. If you have not set up a custom email integration, all emails will send via Alchemer servers with the default noreply@alchemer.com from email address.
If I want to use multiple/different from addresses, do I need multiple integrations?
This depends on whether you are using the SMTP option or the DKIM/SPF option:
- If you need to send via SMTP, a separate integration is needed for each unique email address. For example, one integration for jon.smith@company.net, and a second integration for jane.smith@company.net.
- If you are instead sending via the DKIM/SPF option, you will be configuring the domain portion of the from address i.e. @company.net, and can customize the rest of the from address within each Send Email Action or Email Campaign.
How are unsubscribed contacts handled when using a Custom Email Integration?
Whether you are sending Email Campaigns via the default Alchemer options (from noreply@alchemer.com) or via a Custom Email Integration (SMTP, DKIM & SPF), unsubscribed contacts are handled in the same way.
Should a recipient of an email campaign sent from your account click the unsubscribe link, they will not receive further invites from any campaigns or surveys in your account. Learn more about contact status.
How can I test and troubleshoot SPF configurations?
Alchemer customers are able to use DMARC Analyzer to confirm that they are not exceeding the SPF record inheritance tree DNS lookup limit of 10.
