Default Headers for Dedicated Sending Domains in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Default headers give Sparkforge a fallback From Name and From Email when a campaign’s From address fails DMARC alignment with your dedicated sending domain. Set them at the sub-account level so every email still ships under an authenticated brand identity.

A default header provides a fallback From Name and From Email for outbound mail sent through a dedicated sending domain. When a campaign’s chosen From address fails DMARC alignment, Sparkforge swaps in your default header so the message still authenticates and delivers.

When to Use Default Headers

DMARC fallback: If a campaign From address doesn’t align with your domain’s DKIM/SPF, Sparkforge uses the default header so the message still authenticates.
Brand consistency: A typo or misconfigured From address never reaches the recipient—they see your authenticated domain.
Compliance: Finance, healthcare, and other regulated industries avoid DMARC rejections and quarantines.

Prerequisites

Sub-account access. Only sub-accounts can add dedicated sending domains and set default headers. Agency-level domains do not support per-sub-account headers.
Validated dedicated sending domain. Complete DNS setup (CNAME, DKIM, SPF) for your custom domain (e.g., email.yourbrand.com) and confirm Sparkforge shows a green checkmark under Settings → Email Service → SMTP Service → Dedicated Domain and IP.

Set the Default From Name and From Email

Open the sub-account.
Go to Settings → Email Service → SMTP Service → Dedicated Domain and IP.
Select Set headers under your dedicated domain.
Enter the default From Name and default From Email and save.

The header applies whenever DMARC alignment fails on a campaign sent through this dedicated domain.

How the Fallback Behaves

Campaign Setup

When you build a broadcast or workflow email, you can set a campaign-level From Name and From Email. If you use an unrelated address (for example, sales@differentdomain.com) that doesn’t align with email.yourbrand.com, DMARC will fail.

DMARC Check at Send Time

If alignment passes, the email goes out with the campaign’s chosen From.
If alignment fails, Sparkforge substitutes the configured default header.

What Recipients See

Recipients always see a valid From Name and From Email tied to your authenticated sending domain. The message stays DMARC-compliant and is far less likely to be rejected or flagged as spam.

Example

Dedicated domain: email.yourbrand.com (validated)
Default From Name: YourBrand Support
Default From Email: support@email.yourbrand.com
Campaign From: Jane from YourBrand <jane@anotherdomain.com>

Because the campaign From doesn’t align with the dedicated domain, recipients see YourBrand Support <support@email.yourbrand.com> instead. The email authenticates and delivers.

Confirm It’s Working

Send a test broadcast or workflow email using a non-aligned From address. Check the recipient’s inbox—the visible From should be your default header values, not the unaligned campaign address.

Frequently Asked Questions

Who can set default headers?

Only sub-account users can manage dedicated sending domains and set default headers. Agency-level domains don’t support per-sub-account headers.

What triggers the default header?

Sparkforge runs a DMARC alignment check at send time. If the campaign’s From address doesn’t align with the dedicated domain’s DKIM/SPF, the default header is substituted.

Do I still need DKIM and SPF set up?

Yes. The dedicated domain must be fully validated (CNAME, DKIM, SPF) before default headers do anything. The system uses those records to evaluate alignment.

Will the default header override every campaign?

No. It only kicks in when DMARC alignment fails. Aligned campaigns send under whatever From you configured at the campaign level.

Where do I confirm the domain is validated?

Open Settings → Email Service → SMTP Service → Dedicated Domain and IP. A green checkmark next to the domain means DNS is in place and headers can be configured.