All new Simply.com webhosting plans are automatically set up with standard SPF, DKIM and DMARC records.
SPF records are used to tell other mail servers which mail servers your domain sends mail through. If they receive a mail from a server that is not on the SPF list, they should treat the mail as spam – whereas if the server is on the list of authorised servers, the mail is most likely NOT spam. A correct SPF record can therefore often help you avoid your mails being blocked by spam filters.
Simply add a TXT record on your domain with the following content:
v=spf1 include:spf.simply.com -all
spf.simply.com is a DNS record we maintain, so you are free from having to do it.
You can set up this record with our DNS configuration, which you can find in our DNS Administration.
This record is created on the assumption that you send mail exclusively through servers at Simply.com. If you send through other mail servers (e.g. your internet provider or a newsletter service), you must extend the SPF record yourself with those. Official documentation on SPF syntax can be found here: http://www.open-spf.org/SPF_Record_Syntax
Always ensure your SPF record is 100 % correct, otherwise you risk your outgoing mails not being delivered.
DKIM is a signing of outgoing mail. That is, when you send mail through your system or mail client, it is signed with a key, with the corresponding key stored in a DNS record on the domain. This proves that the person who sent the mail is the same person who owns the domain.
Simply.com DKIM-signs all mails that are sent through websmtp.simply.com, smtp.simply.com (port 587) and our webmail. For this signing to be valid, the following CNAME records must be present in your domain’s DNS zone. These records are automatically included with the “Simply.com DKIM & SPF” DNS configuration and look as follows:
simplycom1._domainkey CNAME dkim1.simply.com
simplycom2._domainkey CNAME dkim2.simply.com
You must DKIM‑sign outgoing mails that are not sent through the above systems, and set up the necessary DNS records for them.
DMARC is a DNS record used to set a policy for how a receiving mail server should react to incoming mails for a domain, whether it should reject mails that are not DKIM or SPF validated. DMARC does not validate mails, but tells the recipient and their server what to do with mails that fail SPF and DKIM validation.
Our standard DMARC record looks like this:
_dmarc CNAME dmarc.simply.com
p=reject
This policy allows you to ensure that all malicious email is stopped when the DKIM or SPF criteria are not met. As an extra bonus, the recipient of the intended malicious email will never see the email in the first place, as it will never be delivered to a spam or quarantine folder.
By default, domains at Simply.com are set up with a p=reject policy.
This is the configuration we, together with Danish authorities, recommend, as it protects the domain best against abuse and spoofing.
p=quarantine
This policy tells participating email receivers that you would like them to treat emails that fail validation with extra caution. When this policy is implemented, emails that breach the DKIM or SPF check are still delivered, but they are marked as spam or placed in quarantine.
p=none
This policy provides no protection for your domain, and should only be used in combination with monitoring tools and RUA or RUF reporting. With a p=none policy, all emails will be delivered even if they fail validation, making your domain vulnerable to, for example, mail‑spoofing.
Regardless of which policy you choose, DMARC should initially be set up as a TXT record with _dmarc as the name and starting with the value v=DMARC1; followed by the desired policy. If you wish to design the DMARC policy for your domain, you can conveniently use https://dmarcian-eu.com for assistance with configuration and monitoring of DMARC.
Article from the support category: Mail
