Emails not sent or go to junk - Setting up DMARC or SPF Record

If you have enabled the email spoofing protection features of DKIM and DMARC on your domain, this may cause emails sent using Arbor to appear in parents' junk folders (Often parents using Gmail or Hotmail services). 

If you aren't using DKIM or DMARC, this article also includes detail of the SPF record you can create to flag Arbor as a valid sender. 

To ensure emails sent by Arbor don’t go to junk complete the steps below:

Setting up DMARC

Step 1 - Add a DMARC policy (including setting up DKIM and SPF records)

The process for doing this differs depending on your DNS provider. For example:

Step 2 - Let us know the email domains you are using

Once you have added the DMARC policy, contact the Support Team if supported by Arbor, or your Support Partner if not supported by Arbor. Let us know what your email subdomains are (e.g.

We will then be able to provide you with DNS records (specific to your domains) for you to addTypically for a trust, there will be a domain for each school, so let us know which domains you want emails to be sent as through Arbor. 

Step 3 - Add DNS records

Once you've sent us the email domains that are in use, we will provide you with a set of CNAME records to add to your provider, that specify Arbor is a valid sender for your specific domains. 

To add a new record:

  1. Go to your domain’s DNS records.
  2. Add a record to your DNS settings, selecting CNAME as the record type.
  3. Use the Host and Value fields we've given to you (these will look similar and to create CNAME records with the first value in the Host field, and the second in the Value field. For example, in AWS Route 53, this looks like the example below
  4. Save your record.



Step 4 - Let us know you're ready to go

Once you have added the records we've provided, let us know so we can verify everything is working. After that, you should be able to safely send emails from Arbor via your domains!

Adding an SPF Record

If you aren't using DKIM or DMARC, you'll just need to add an SPF record to your email policy, to state that Arbor is a valid sender. The SPF record is as follows:

ip4: ip4:

Please note that this example does not include other SPF records that you may need to include for other services, such as Microsoft O365 or Google Workspace. For instance, a complete SPF record for O365 may look something like v=spf1 v=spf1 -all


If you find that our SPF record pushes the number of DNS lookups over 10, we'd recommend adding the following flattened record instead, which includes fewer lookups:

v=spf1 ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4:

Was this article helpful?
4 out of 16 found this helpful
I'm still stuck!



Article is closed for comments.