Setting Up SPF Records for Learn Amp Emails
Overview
Sender Policy Framework (SPF) is an email authentication standard that helps prevent email spoofing. If your organisation uses custom email domains with Learn Amp, setting up SPF records ensures reliable email delivery and helps prevent Learn Amp notifications from being marked as spam.
Learn Amp partners with Mailgun for email delivery. This guide explains how to configure SPF records to authenticate emails sent through Learn Amp.
Functionality Breakdown
What SPF Does
SPF records tell email servers which mail servers are authorised to send emails on behalf of your domain. When Learn Amp sends notification emails:
The receiving mail server checks your domain's SPF record
It verifies that Mailgun (Learn Amp's email provider) is authorised
If authorised, the email is more likely to reach the inbox rather than spam
When You Need SPF Configuration
You should configure SPF records if:
Learn Amp emails are consistently going to spam folders
Your organisation has strict email security policies
You want to improve overall email deliverability
Pre-requisites
Role Requirements
Action | Required Roles |
|---|---|
Configure SPF records | IT Administrator (DNS access required) |
Request custom email domain setup | Owner, Admin |
Verify SPF configuration | IT Administrator |
⚠️ Warning: SPF configuration requires access to your organisation's DNS settings. Work with your IT team to make these changes.
Quick Start Guide
If You Don't Have an Existing SPF Record
Create a new TXT record in your DNS with:
v=spf1 include:mailgun.org -allThe -all mechanism indicates this SPF record is the only one used to authenticate mail for your domain.
If You Have an Existing SPF Record
Add Mailgun to your existing record. For example, if your current record is:
v=spf1 a mx include:_spf.google.com include:spf.protection.outlook.com -allUpdate it to include Mailgun:
v=spf1 a mx include:_spf.google.com include:spf.protection.outlook.com include:mailgun.org -all💡 Tip: Add the Mailgun inclusion before the -all or ~all mechanism at the end.
Verifying Your SPF Record
Wait 24-48 hours for DNS propagation
Use an online SPF checker tool to validate your record
Send a test notification and verify it reaches the inbox
FAQs
Q: What's the difference between -all and ~all?-all indicates a hard fail—emails not matching the SPF record should be rejected. ~all is a soft fail—emails may be accepted but marked as suspicious. Use -all for stricter security.
Q: Can I have multiple SPF records for one domain?
No. You must have only one SPF record per domain. If you need to authorise multiple email services, combine them into a single record.
Q: What if my SPF record has too many DNS lookups?
SPF records are limited to 10 DNS lookups. If you exceed this, consider using SPF flattening tools or consolidating your email services.
Q: How long does it take for SPF changes to take effect?
DNS changes typically propagate within 24-48 hours, though some providers may be faster.
Troubleshooting
Issue | Solution |
|---|---|
Emails still going to spam | Verify the SPF record is correctly published. Use online SPF checkers to validate. Allow 24-48 hours for DNS propagation. |
SPF validation failing | Ensure there's only one SPF record. Check for syntax errors. Verify all includes are correct. |
Too many DNS lookups | Review your SPF record for unnecessary includes. Consider using IP addresses instead of includes where possible. |
Can't access DNS settings | Contact your IT administrator or domain registrar for access. |