Merging SPF for an Additional Email Sender (Adding WeGive Alongside Microsoft 365/Outlook or Another Provider)

If your organization already sends email from your domain through another provider — most commonly Microsoft 365/Outlook — and you’re now setting up WeGive to send from that same domain, you don’t create a second SPF record. A domain can only have one SPF TXT record; adding a second one causes mail servers to treat SPF checks for your domain as a permanent error, which can hurt deliverability for all your senders, not just WeGive. Instead, you add WeGive’s sending authorization into your existing SPF record as an additional include entry.

Step 1: Find Your Current SPF Record

Look up your domain’s existing SPF TXT record with your DNS provider, or with a lookup tool like MXToolbox. It will look something like this if you’re sending through Microsoft 365/Outlook:

v=spf1 include:spf.protection.outlook.com -all

Step 2: Add WeGive’s Mailgun Include

When you add your domain under Settings → Email Settings in WeGive (see Adding a Custom Email Domain), WeGive shows you the SPF value to add for your domain. Rather than replacing your existing record, merge WeGive’s include:mailgun.org into it, keeping the include(s) you already have:

v=spf1 include:spf.protection.outlook.com include:mailgun.org ~all

Update the same TXT record at your DNS provider — don’t create a new one. Order of the include entries doesn’t matter.

Step 3: Verify in WeGive

Return to Settings → Email Settings and click Verify on your domain once the DNS change has propagated (this can take anywhere from a few minutes up to 24–48 hours). WeGive checks the merged record and marks your domain Authenticated once it resolves correctly.

Do I Need to Change My DMARC Record Too?

No. DMARC is a single policy record for your whole domain (_dmarc.yourdomain.org), not a per-sender list, and it passes as long as either SPF or DKIM authenticates the message for your domain. Adding an additional sender through an SPF include doesn’t require any DMARC change on its own.

Troubleshooting

Issue	What to do
Verification fails after merging	Confirm you edited the same TXT record rather than creating a second one — a domain with two SPF records will fail verification for every sender, not just the new one.
Not sure what your current SPF record contains	Look it up with your DNS provider or a tool like MXToolbox before making any change, so you don’t accidentally drop your existing provider’s `include`.
Still failing after several hours	Double-check both `include` values are present with no typos, and that only one SPF TXT record exists for the domain.

When to Contact Support

Reach out to [email protected] if you’re unsure how to safely merge the record, or if verification keeps failing after confirming only one SPF record exists. Include your domain and the current contents of your SPF record.

​Step 1: Find Your Current SPF Record

​Step 2: Add WeGive’s Mailgun Include

​Step 3: Verify in WeGive

​Do I Need to Change My DMARC Record Too?

​Troubleshooting

​When to Contact Support

​See Also