Deliverability settings and SPF/DKIM
If your team uses SMTP forwarding channels in Front, we strongly recommend that you set up specific SPF/DKIM entries in your DNS configuration. Whenever there are missing SPF/DKIM records for an email domain you use in Front, you will see warnings in the app indicating this set up step has not been completed.
Follow the steps in this article to add your SPF/DKIM records for each email domain you use to send messages in Front. This is advanced material that would best be done by an IT admin or someone that fully understands the impact of DNS records.
How it works
What are SPF/DKIM records?
SPF/DKIM records are industry-standard security mechanisms that authorize Front to send emails on our customers’ behalf. For email channels using SMTP forwarding, it’s critical to correctly configure SPF/DKIM records for your email domain.
Impact on SMTP channels
If you are using SMTP channels to send emails in Front, we strongly recommend that you authorize SendGrid to send emails on your behalf by setting up specific SendGrid SPF/DKIM entries in your DNS configuration. Configuring SPF/DKIM will:
- Improve email deliverability
- Ensure that emails you send from Front do not get marked as spam in your recipient's inbox, or caught in their spam filters
- Remove "via sendgrid.net" from the From: address in your outbound emails
SPF/DKIM settings do not impact your ability to receive inbound emails in Front. If your email channel uses SMTP forwarding, then once you have validated the channel in Front any emails received by that domain will appear in your Front inbox.
Note: Wix, HostGator, SiteGround and Squarespace do not support creating the required MX record. If you need to use one of these DNS providers, we recommending configuring custom SMTP for these channels to send mail via your own mail servers, using your existing DNS records.
Gmail and Office 365 channels
If your email channel uses Gmail sync or Office 365 sync, you do not need to configure SPF/DKIM records, as we rely on the Gmail and Office 365 APIs to send and receive email.
For Google Groups and for Gmail or Office 365 channels set up with SMTP forwarding, you should add SPF/DKIM records for your domain.
There is one deliverability settings page visible to Company Admins where you can configure records for all your email domains in one place. If you are not a Company Admin, you will not see this settings page and will need to get your admin’s help.
Follow these steps to add your SPF/DKIM records for each domain you use to send emails from Front.
Click the gear icon on the top right of Front and into the Company settings tab.
Click on the Deliverability tab. Here, company admins can configure SPF/DKIM records. This page will only be visible to Company Admins after they add at least one team SMTP channel.
Note: If you do not see the Deliverability tab, it is likely because only individual SMTP inboxes have been added. If this is the case, please follow the instructions here to add SPF/DKIM records for individual SMTP channels.
You will see a list of your SMTP channel domains under Domains on the left. Any email domains with missing SPF/DKIM records will have a yellow warning icon. Select a domain to view its DNS records.
Copy the Values from the DNS records in Front, and add them as a DNS record in your DNS provider settings. Each DNS provider offers a different UI to add these entries to the DNS. Please ask your IT department if you're unsure how to do this.
Here are instructions for the most popular providers:
Once you've added the DNS settings in your DNS provider settings, you can come back to Front and click Check DNS settings.
This will trigger a check by SendGrid to verify that your DNS configuration is correct. Be aware that SendGrid might not see your changes before the time specified in your DNS TTL settings. Wait a few seconds and the validation result will appear (with the encountered errors if any).
When you’ve successfully added the SPF/DKIM records, the warning icon will be removed from the channel name in the list and the DNS records will say Verified.
Whenever there are missing SPF/DKIM records for an individual SMTP channel using a domain that isn't present in the Deliverability tab, Company Admins will find the DNS records in a different location.
Click the gear icon on the top right of Front and into the Company settings tab. Go to the Teammates section and select the teammate.
Go to the teammate's Individual inboxes settings, and select the inbox that contains the SMTP channel.
Go to the inbox's Channels settings, and expand the channel settings for the SMTP channel.
Scroll to the Improve delivery rates - SPF / DKIM setting, and expand the setting.
Follow steps 4-6 from the section above to complete the setup.
Tips for adding DNS records
Each DNS provider has their own format of how the records should be entered, but here are some general tips on how to enter Front's records, that should apply to most DNS settings:
- 1st DNS Record: The Value that you copy into your DNS settings should not include the 100 in the beginning nor the period (.) at the end.
- 2nd DNS Record: The Name field that we display lists the subdomain before your actual domain name, so in the example screenshots in the instructions above, the DNS subdomain field you enter would be front-mail. Do not include your own domain name.
- 3rd DNS Record: Similar to the 2nd DNS Record in the Name field, the subdomain is the part before your own domain name.
In your Deliverability settings, you will see a warning for any domains that do not have SPF/DKIM records set.
Inbox and channel settings
If an SMTP channel uses an email domain that does not have SPF/DKIM records set, a warning will appear in your Inboxes list, as well as in the Channels settings for the inbox containing that channel.
DMARC is an optional deliverability record unrelated to Front that your IT team may already have in place. Learn more about how DMARC DNS records work with Front in our Front email deliverability and DMARC records article.
I already have MX records in place, do I still need to add Front's MX record?
Yes. The MX DNS record that Front asks you to configure is different from your "core" existing MX record.
Your existing MX record will have a host value of @ - this is what mail servers use to determine how to direct mail addressed to your domain to the right place. The MX record Front asks you to configure has a host value of front-mail. This record sits in a different place, and will not impact your inbound message flow. When configuring these three DNS records for Front, you should be adding three new records, not modifying any existing records.
I see SPF/DKIM records missing in Front but don't have experience configuring DNS records, what should I do?
If you see SPF/DKIM records missing in Front, but are unable to make changes to your DNS configuration yourself, you can click Ask your IT team to make this change at the bottom of your DNS records in Front. This will produce a pre-filled template that you can send to your admin or IT team with all the information needed to configure SPF/DKIM records.
Cori Morris Hi Cori,
we use network solutions. i don't see a way to add the values shown on the 1st, 2nd and 3rd DNS records into network solutions. front mentions that 2 records are TXT and 1 is MX but it doesn't indicate what is the Host / TTL and TEXT value we should input on the DNS administrator, in network solutions. can you please help?
Just sayin... I finished 3 other trials with different companies before choosing Front and they have instructions that go into more detail or at least a link to the 'how to' page for each of the providers. The instructions are not clear at all. I've done cname changes and other things like that and have been able to figure it out.
This was my experience (and mistake): I had to contact bluehost, they added the changes, then I realized that it completely disabled my ability to send emails through bluehost because the MX settings were changed (and I didn't realize that was what would happen.)
After, it required another call to figure out what the original settings were and to re-enable my ability to send email until I was ready.
I was still on a trial with Front and not ready to use only the Front inbox. Emails were still being sent to my Gmail through pop3. The poor explanation of these settings lead me to set this up (to ensure deliverability) without realizing the consequences of getting it wrong.
I looked at the settings the Bluehost tech entered and there is honestly no way I would have figured it out on my own.
I think these instructions could be 'rewritten for simple folk' that are using this software as an email management solution without assuming we all have an IT team to handle this. At least with a warning not to make any changes unless you are 100% certain what you are doing.
I got these instructions in my email late last night and now I have the team that is using front freaking out because they are getting the warning. Getting these instructions last min is pretty disheartening. Also I cannot make the changes to the MX records in the fashion that your suggest here using HostGator. I need support but cannot find a way to get personal support for our specific issue. Very frustrating all around!
I have two out of three working. But then I come back to Front and it tells me all three are not working again.
This is very confusing, you should definitely have a lot more support for your users.
How would I change this if my email is set up with Google?
Right now your instructions don't seem to work.
And I recently posted and argued on a big e-commerce forum about how Front was better than Gorgias....... :(
Hi Mark , processing incoming spam (inbound mail) and your SPF/DKIM settings (outbound mail) are two separate functions, so the deliverability warnings you're seeing should be unrelated to your Google spam filter. If you have any specific questions about your setup, please email us at email@example.com so we can look into your account without giving any personal information here :)