Great question—let me clear this up for you: Mailchimp does support SPF authentication, but its presentation in the admin interface might be throwing you off, and it’s easy to miss the relevant details if you’re looking in the wrong place.

Here’s a breakdown of how it works:

• Why you don’t see SPF in the Authenticate flow: Mailchimp’s domain authentication wizard prioritizes DKIM and custom Return-Path setup (these are often more straightforward to implement via their guided interface). SPF, however, requires modifying your existing domain’s SPF record (or creating one if you don’t have it)—and since each domain can only have one SPF record, Mailchimp can’t generate or manage this for you directly. Instead, they expect you to merge their required entry into your existing record manually.
• The required SPF entry for Mailchimp: You need to add include:servers.mcsv.net to your domain’s SPF TXT record. Examples of how to do this:
  • If you don’t have an SPF record yet, create a new TXT record with the value: v=spf1 include:servers.mcsv.net ~all
  • If you already have an SPF record (e.g., v=spf1 a mx ~all), update it to include Mailchimp’s entry: v=spf1 a mx include:servers.mcsv.net ~all
• Verifying your SPF setup: After updating your DNS records (which can take 1–24 hours to propagate), you can use tools like MXToolbox to check if your SPF record includes servers.mcsv.net. Alternatively, return to Mailchimp’s domain authentication page and refresh—they should detect the valid SPF configuration once DNS propagates.

You’re absolutely right that SPF is a critical part of domain authentication for email deliverability—it helps receiving servers confirm that Mailchimp is authorized to send emails on your domain’s behalf. Don’t skip this step even if it’s not front-and-center in Mailchimp’s interface!

内容的提问来源于stack exchange，提问作者user1154435