Improving email delivery from your ChurchSuite account
This article explains how to complete the domain verification process, so that ChurchSuite's email service has permission to send emails on your church's behalf. Domain verification increases email security and deliverability, while also helping protect your domain reputation from 'spoofing'.
Overview - domain verification
Until your church's domain name has been verified, all outbound emails sent from your ChurchSuite account will show as being sent 'From' yoursubdomainname+user-username.out.churchsuite.com, as "out.churchsuite.com" is a verified domain.
Note that the 'Reply to' email address will always show your user's email address, so that replies are correctly routed. However, there are a small number of email hosts that do not respect 'reply to', which could result in email replies not being delivered back to the user. We therefore encourage you to take time to complete your church's domain verification. This only needs to be done once for each registered email domain used by your users for sending emails from within ChurchSuite - it doesn't need to be done for every user!
By way of explanation, ChurchSuite makes use of an email service called Mandrill (mandrill.com), the email service behind the incredibly popular mailing list system MailChimp (mailchimp.com), which immediately gives your emails a greater chance of not being diagnosed as spam. There are, however, a few things you can do to improve your email deliverability...
If you're sending out an email within ChurchSuite from your personal Hotmail address (for example), Hotmail will know that the email didn't originate from their email servers, even though the "From" address suggests that it should have done — this increases the chances of Hotmail marking the email as spam. We would therefore strongly recommend that your ChurchSuite Users use an email address that is specific to your church and makes use of your church's domain name, e.g. firstname.lastname@example.org. We also recommend you verify your church's domain name with Mandrill - we've provided a simple-to-use "Mandrill Integration" in the Administrator > Integrations section of ChurchSuite. Here's how to complete this...
Using the Mandrill Integration to verify your domain name
Begin by entering a valid email address within your church's domain - ideally an email address that you receive replies to. Click "Save and Proceed". Now check your email inbox. Mandrill Client Services will have sent you a domain verification email that must now be forwarded to us at email@example.com. If the email doesn't arrive, check your spam folder. The email comes from firstname.lastname@example.org and contains information that we at ChurchSuite need in order to complete the verification of your domain against your ChurchSuite account.
Note that you can abort and reset the Integration at any time in order to request another email from Mandrill, if you need to. Be aware, however, that each Mandrill verification email causes all previously requested emails to expire, so you must send us the latest email that you receive.
This stage simply involves ticking to confirm that you have forwarded the Mandrill email to us at ChurchSuite Support. Once we receive that email and process it, we'll send you a confirmation email back advising that you can proceed to the final stage. Now you can tick the box in Stage 2 and click "Save and Proceed".
This stage can be trickier as it requires a little technical 'know how' and access to the DNS settings in your domain host's user control panel. Essentially you are going to add two new text records (TXT) to your DNS settings. Navigate to the advanced DNS settings in the control panel for your domain host. Follow your host's instructions for adding the following two DNS records. Your domain host should provide support articles on how to add DNS text records; alternatively you may wish to reach out to their online support for help with this.
DNS Text Record 1: Add a DKIM record to your domain name
A DKIM record authorises an email service to send out emails on behalf of your domain name, in this case, it authorises ChurchSuite to send out emails from email@example.com.
You will need to create a new TXT record for mandrill._domainkey.yourchurchdomain.com (where yourchurchdomain.org is your church's domain name). Note that some host providers will automatically append your church's domain name to the DNS record, and may simply require you to add in the prefix part, i.e. mandrill._domainkey. For example, kingschurch.org would be mandrill._domainkey.kingschurch.org
For your TXT record add the following TXT value (be sure to copy and paste the full value from the box below - it ends with a semicolon):
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
DNS Text Record 2: Add an SPF record to your domain name
An SPF record is similar to a DKIM record in that it authorises emails to be sent out from your domain name by a third-party service.
You will need to create (or edit an existing) a TXT record for yourchurchdomain.org (where yourchurchdomain.org is your church's domain name) with the following value (be sure to copy and paste the full value below):
v=spf1 include:spf.mandrillapp.com ?all
Note: Most domain hosts do not require a host name to be entered - the text value above is sufficient. If an entry is required in the host name field, try entering just the @ symbol (which symbolises your root domain name), or enter your domain name in full. Do not enter mandrill._domainkey in the host name field for SPF.
If you have an existing SPF record, with existing text for your domain name (perhaps with other 'include' statements), you need simply edit the existing record by adding include:spf.mandrillapp.com before the final all part - be careful not to overwrite any of the existing 'include' statements - just append include:spf.mandrillapp.com.
Note that you can only have one SPF record in DNS. While you might have multiple DKIM records, you should only have one SPF record in your DNS.
If you have more than one domain to verify, you can simply click "Add another domain" button at the top of the Integration page, and repeat Stage 1 again. - ChurchSuite tracks the progress of each domain's verification through each stage.
Once you have completed adding the two DNS records and saved all your changes, switch back to ChurchSuite and head back into the Mandrill integration again. It can sometimes take a few hours for DNS changes to propagate over the internet. However, if you've done everything correctly then the Mandrill Integration will show four green ticks and the progress bar will be 100% green. Click "Finish" to close and complete the Integration - you're all done, and your domain has been verified! Outbound emails sent through your ChurchSuite account will now showing correctly as originating from the email address within your verified domain (if a domain email address has been correctly associated with each User's profile).
Remember, you only need to complete domain verification once for each of your church's domains. It is not necessary to verify each individual user's email address that exists within your domain.