Agencies
Why Your Newsletter Tool Passes SPF but Fails DMARC
Rodney Hall, COO— AI-assisted and reviewed prior to publication.

Your newsletter tool passes SPF but fails DMARC because SPF authenticated the platform's bounce domain, not yours. DMARC requires the domain that passed SPF to match the visible From domain in relaxed or strict mode. When your platform uses bounces@platform.com as the envelope sender while you send from you@yourdomain.com, SPF alignment fails regardless of SPF passing.
What alignment means in a DMARC check?
SPF pass but DMARC fail occurs when "your SPF check passed (the sending IP is authorized for the Return-Path/envelope domain), but that envelope domain does not align with the visible From: header domain" (courier.com). DMARC does not ask whether SPF succeeded. It asks whether the domain SPF authenticated shares an organizational domain with the RFC5322.From header the recipient sees. That match is alignment, and it determines the DMARC result.
DMARC "passes or fails a message based on how closely the domain in the From: header matches the sending domain specified by either SPF or DKIM. This is called alignment." (support.google.com) Most email platforms set the Return-Path (the envelope sender, also called RFC5321.MailFrom) to their own bounce-handling domain by default. SPF authenticates the ESP's domain, not yours (healthcheckemail.com), so SPF alignment fails even when the SPF check itself returns pass.
A worked example: newsletters sent through a platform
You send a campaign with the visible From address set to marketing@yourdomain.com. Your platform routes bounces to its own infrastructure and sets the envelope sender to bounce-abc123@mail.platform.net. When the message arrives, the receiving server performs these checks:
SPF check: The server extracts the envelope sender domain mail.platform.net, queries its SPF record, and verifies the sending IP is authorized. Result: spf=pass.
SPF alignment check: DMARC "compares the From header domain against the domain in the envelope sender" (emailindustries.com). The From domain is yourdomain.com, the envelope sender domain is mail.platform.net. These do not share an organizational domain, so SPF alignment fails.
DKIM alignment check: If the platform signed the message with d=mail.platform.net, that domain also does not align with yourdomain.com. DKIM alignment fails.
DMARC result: DMARC fails when "neither path satisfies both halves" (dmarctrust.com). The message authenticated successfully through SPF and possibly DKIM, but neither authenticated your visible domain.
How do I set up custom DKIM in my platform?
The most reliable fix is to configure DKIM signing under your own domain. DKIM alignment "survives forwarding, while SPF alignment never does" (showdns.net), making it the stronger path for most senders.
Log in to your email platform and locate the domain authentication or sender authentication section. The exact label varies (SendGrid calls it "Sender Authentication", ActiveCampaign calls it "Sending Domain"), but the process is similar across platforms. Enter the domain you use in the From address. The platform will generate DNS records, typically two CNAME records with names like s1._domainkey.yourdomain.com and s2._domainkey.yourdomain.com.
You "need to create a CNAME (like pmbounces.yourdomain.com)" and publish the records in your DNS zone. Wait for DNS propagation (usually under an hour), then return to the platform and verify. Once verified, the platform signs outgoing mail with d=yourdomain.com, which aligns with your From domain and satisfies DMARC.
How to configure a custom return path for SPF alignment
A custom return path aligns the envelope sender with your domain, fixing SPF alignment. In SendGrid, "check Use custom return path" and "type alphanumeric characters for your preferred subdomain" during domain authentication setup. The platform will generate a CNAME record like bounce.yourdomain.com pointing to its mail infrastructure.
Publish that CNAME record in your DNS. Once verified, the platform uses bounce.yourdomain.com as the envelope sender. This subdomain "enab[les] relaxed SPF alignment for DMARC" because bounce.yourdomain.com and yourdomain.com share the same organizational domain.
Not every platform supports custom return paths. When a platform does not offer it, "your email can still pass DMARC tests with a properly configured DKIM record". DMARC requires only one aligned pass, not both. If your platform limits you to DKIM, that is enough.
Check your authentication in the free AI-visibility check (/check)
After configuring DKIM and optionally a custom return path, send a test message and inspect the headers. Look for dmarc=pass in the Authentication-Results header. If the result still shows dmarc=fail, check which domains appear next to spf=pass and dkim=pass. The "d= domain in the DKIM result and the envelope sender domain in the SPF result are the two things to check. If either matches your From domain (exactly for strict, organisationally for relaxed), you're aligned."
DMARC aggregate reports (RUA) provide a volume view of alignment across all mail. Configure the rua tag in your DMARC record to receive daily XML reports showing which sources pass, which fail, and why. "Confirm in aggregate reports a day or two later that the source now shows an aligned pass at volume", not just for test messages. Many agencies use ActiScore's pricing (/pricing) plans to audit DMARC alongside nine other categories, particularly when evaluating client domains before onboarding.
When relaxed alignment is not enough
Strict alignment means "the sender domain name must exactly match the corresponding d=domainname in the DKIM mail headers". If the client's DMARC record specifies aspf=s or adkim=s, subdomain alignment will not pass. A From domain of newsletter.yourdomain.com will fail strict alignment against a DKIM signature with d=yourdomain.com, even though both share an organizational domain.
The fix is to sign with the exact subdomain or change the From domain to match the DKIM signing domain. Strict alignment is rare outside highly regulated environments, but the guide (/guide) explains when you might encounter it and how to audit for it at scale across client accounts.
Written with AI assistance. Rodney Hall is responsible for this article.
Common questions
Why does SPF pass but DMARC still fail?
SPF passes but DMARC fails because SPF authenticated your platform's bounce domain rather than your visible From domain. DMARC requires the domain that passed SPF to align with the From header domain in relaxed or strict mode. When your email platform uses an envelope sender like bounces@platform.com while you send from you@yourdomain.com, the SPF check succeeds for the platform's domain but SPF alignment fails because the two domains don't share an organizational domain.
What is DMARC alignment?
DMARC alignment is the match between the domain authenticated by SPF or DKIM and the visible From domain in your email header. DMARC doesn't just ask whether SPF or DKIM passed—it asks whether the authenticated domain shares an organizational domain with the RFC5322.From header the recipient sees. For relaxed alignment, the organizational domains must match. For strict alignment, the domains must match exactly. DMARC passes when at least one authentication method both passes and aligns.
How do I fix DMARC failure with custom DKIM?
Configure your email platform to sign messages with a DKIM signature using your own domain. Log in to your platform's domain authentication section, enter the domain you use in From addresses, and the platform will generate CNAME records like s1._domainkey.yourdomain.com. Publish these records in your DNS zone, wait for propagation, then verify in the platform. Once verified, the platform signs outgoing mail with d=yourdomain.com, which aligns with your From domain and satisfies DMARC even if SPF alignment fails.
What is a custom return path and do I need it?
A custom return path is a subdomain on your domain that your email platform uses as the envelope sender, aligning SPF with your From domain. Platforms like SendGrid let you configure bounce.yourdomain.com to point to their infrastructure via CNAME, so the envelope sender uses your organizational domain and passes SPF alignment. You don't strictly need it—DMARC requires only one aligned pass, so DKIM alone is sufficient. Custom return paths are useful for redundancy because DKIM alignment survives forwarding while SPF alignment never does.
How do I check if my DMARC is passing after setup?
Send a test message and inspect the email headers for an Authentication-Results header showing dmarc=pass. Check which domains appear next to spf=pass and dkim=pass—the d= domain in the DKIM result and the envelope sender domain in the SPF result must align with your From domain. For volume verification, configure the rua tag in your DMARC record to receive daily aggregate reports showing which sources pass or fail and why. Confirm in aggregate reports a day or two later that mail from your platform shows an aligned pass at volume, not just in test messages.
