One of our most appreciated features is the ability to send directly from your own domain. When emails sent from your company, email servers and anti-spam software may look at that email and determine that it's not a genuine email from your company and may prevent delivery or send to your SPAM/Junk folder.
There are a number of mechanisms to optimize inbox delivery, each mechanism is detailed below.
All of these changes involve updating the DNS records for your domain, so you will need to have access (or know who has access) to make these changes. They are very simple changes to make and will take a matter of minutes for someone who has access.
Some things to note:
In addition to the configuration in this guide, you should run a health check on your own domain to ensure that there are no red flags - use IntoDNS to test your domain. If you have any questions about the results, contact us at email@example.com for advice.
DKIM stands for Domain Keys Identified Mail. DKIM records are a way of authenticating emails by adding a digital signature (also known as a private key) to every email that is sent. This private key must match with a corresponding public key that is located in the DNS settings for your domain. When an email client sees that the private and public keys match, it knows that the email is a genuine email from your company.
SPF is an acronym for Sender Policy Framework and is a way to prevent forged sender addresses in email. It is a DNS record you can add to your domain to list all mail servers/services that are permitted to send email on your behalf. If you do not have an SPF record configured, your email client will not be sure that the received email is genuine. In this situation, any tests of the SPF record by email clients will be "Neutral". By adding an SPF record, you remove this doubt and give the email a greater chance of reaching the inbox - a test of the SPF will result in a "Pass". If the SPF is incorrect or someone tries to send an email pretending to be you (forging the email header), the SPF will "Fail" and there is a good chance it will go to SPAM.
DMARC is an acronym for Domain-based Message Authentication, Reporting and Conformance. DMARC takes the two earlier principles (DKIM and SPF) and uses both to authenticate the email. In addition, DMARC adds an extra level of reporting for the Email Service Provider - we get alerted if there is an issue with the SPF or DKIM record for any senders on our platform. DMARC has become widely accepted as the de facto way of authenticating the email - it helps protect the sender, and it discourages spammers and cyber-criminals from trying to spoof domains that have DMARC records in place.
For DKIM, we need to create a unique public key for your domain.
For SPF, we will take a look at your existing SPF record (if you have one) and provide the amended record that includes our details. If you didn't have an SPF record, we will provide one that will work for you. Note - it won't have any negative impact on your regular corporate emails.
For DMARC, we need to verify that DKIM and SPF have been configured correctly first (DMARC relies on SPF and DKIM). Once verified, we will provide the details.
To start this process, please contact firstname.lastname@example.org for further assistance.
From the main menu, open the "Tools" submenu and choose "Test for SPF/DMARC".
You will be prompted for your domain:
Enter your domain and click the "Check" button. If everything is OK, you will see these messages at the bottom of the screen:
If you have any issues, please contact email@example.com for further assistance.