Default Headers for Dedicated Sending Domains

A “default header” provides a fallback From Name and From Email for outbound messages sent via a dedicated sending domain for all emails. This ensures deliverability and brand consistency.

TABLE OF CONTENTS

• When to Use Default Headers
• Prerequisites
• Setting Default Headers (From Name & From Email)
• How Default Headers Work in Practice
• Example: Finished Default Header Setup
• Best Practices & Considerations
• Common Troubleshooting Scenarios

When to Use Default Headers

• Fallback for DMARC Failures: If a campaign’s “From” address does not align with your dedicated sending domain’s DKIM/SPF records, OmniReach will use default header so that the message is still authenticated.
  
  

• Maintain Consistent Branding: Even if a typo or misconfiguration causes a non-aligned “From,” recipients will see your brand’s domain in the From field rather than a rejected address.
  
  

• Regulatory/Compliance Requirements: Industries requiring strict email authentication (finance, healthcare, etc.) should configure default headers to avoid DMARC rejections or quarantines.

Prerequisites

Before you can configure default headers, ensure that:

1. You’re in a Sub-Account
   

   • Only sub-accounts can add and manage dedicated sending domains and set default headers. Agency-level domains do not support per-sub-account default headers.
     
     

2. Dedicated Sending Domain Is Added and Validated
   

   • You have completed DNS setup (CNAME, DKIM, and SPF) for your custom sending domain (e.g., email.yourbrand.com).
     
     

   • OmniReach displays a green checkmark indicating your domain is validated under Settings → Email Service → SMTP Service → Dedicated Domain and IP

Setting Default Headers (From Name & From Email)

Navigate to Sub-account Settings - Email Service -> SMTP Service -> Dedicated Domain and IP -> Set headers under dedicated domain.

How Default Headers Work in Practice

1. Campaign Configuration
   
   

   • When creating a broadcast or workflow email, you can set a campaign-level “From Name” and “From Email.
     
     

   • If you intentionally use a different “From Email” (e.g., sales@differentdomain.com) that does not align with your dedicated domain (email.yourbrand.com), DMARC will fail.
     
     

2. DMARC Check & Fallback
   
   

   • At send time, OmniReach checks DMARC alignment between the campaign’s “From” address and the sending domain’s DKIM/SPF records.
     
     

   • If alignment passes: The email goes out with the campaign’s chosen “From.
     
     

   • If alignment fails: OmniReach use the default header you configured under that dedicated domain.
     
     

3. Recipient Experience
   
   

   • Recipients see a valid “From Name” and “From Email” that matches your authenticated sending domain.
     
     

   • The email remains DMARC-compliant and is less likely to be rejected or flagged as spam.

Example: Finished Default Header Setup

Example scenario

• Dedicated sending domain: email.yourbrand.com (validated)
  
  

• Default Header From Name: YourBrand Support
  
  

• Default Header From Email: support@email.yourbrand.com

Broadcast/workflow email configured by the user

• Campaign From Name: Jane from YourBrand
  
  

• Campaign From Email: jane@anotherdomain.com (does not align with email.yourbrand.com)

What Happens at Send Time

• If the campaign From Email aligns with the dedicated sending domain, recipients see:
  
  

  • From: Jane from YourBrand <jane@email.yourbrand.com> (or whatever aligned address you selected)
    
    

• If the campaign From Email does NOT align and DMARC alignment fails, OmniReach applies the Default Header and recipients see:
  
  

  • From: YourBrand Support <support@email.yourbrand.com>

How to Confirm It Worked

• Send a test email using a non-aligned From Email (domain mismatch).
  
  

• Check the received email’s “From” address and confirm it matches the Default Header.

Best Practices & Considerations

1. Configure Default Headers Before Sending: Always set up your fallback header prior to launching major campaigns. If DNS or DMARC misconfiguration occurs, your default header will kick in automatically.
   
   

2. Monitor Replies: The default “From Email” can be any address at your sending domain, but ensure mailboxes or aliases are monitored (e.g., support@yourbrand.com forwarding to the correct team).
   
   

3. Test Before Scaling: Send a small internal test using a non-aligned “From” address to confirm OmniReach defaults properly. Check both inbox placement and DMARC status.
   
   

4. Understand Propagation Delays: Changing DNS (especially DKIM/SPF/TXT records) can take up to 48 hours to fully propagate. Without default headers, messages sent during propagation may be rejected.
   
   

5. Segregate by Sub-Account: If you manage multiple brands or departments, create separate sub-accounts—each with its own dedicated domain and default headers—for isolated control.

Common Troubleshooting Scenarios