In this article
Why We Released This Feature Three Validation Cases We Check Case 1: No DMARC Record Found Solutions for Case 1 Case 2: Invalid DMARC Record Format Solutions for Case 2 Case 3: Domain Mismatch Solutions for Case 3Why We Released This Feature
Starting February 2024, Gmail and Yahoo require proper email authentication. Without this validation:
Emails silently land in spam folders
Major providers reject your messages
Low deliverability with no explanation
Sender reputation damage
Reduced campaign ROI
Our validation catches these issues BEFORE they hurt your campaigns.
Three Validation Cases We Check
Our system validates three critical email configuration issues:
Case 1: No DMARC Record Found
ERROR MESSAGE: "No DMARC record found for this domain. Please try a different email."
WHAT IT MEANS: Your 'From' email domain doesn't have any DMARC record configured in DNS.
EXAMPLE SCENARIO:
Sender Domain: inbox.yourdomain.com (authenticated)
From Email: [email protected]
Issue: yourdomain.com has no DMARC record
Solutions for Case 1
PERMANENT SOLUTION (1-2 hours):
Add a DMARC record to your main domain's DNS:
| Field | Value |
|---|---|
| Record Type | TXT |
| Name/Host | dmarc.yourdomain.com |
| Value | v=DMARC1; p=none; rua=mailto:[email protected] |
| TTL | 3600 (or default) |
QUICK FIX (5 minutes):
Change your 'From' email to match your authenticated sending domain:
Current: [email protected]
Change to: [email protected]
Case 2: Invalid DMARC Record Format
ERROR MESSAGE: "Invalid DMARC record format detected for the Sender Email's domain. Please use a different email."
WHAT IT MEANS: Your domain has a DMARC record, but it contains syntax errors or invalid configuration.
COMMON INVALID EXAMPLES:
Wrong version: v=DMARC2; p=none;
Invalid policy: v=DMARC1; p=invalid;
Missing semicolons: v=DMARC1 p=none
Wrong email format: [email protected] (missing mailto:)
Solutions for Case 2
CHECK THESE COMMON ISSUES:
| Issue | Wrong | Correct |
|---|---|---|
| Version | v=DMARC2 or v=dmarc1 | v=DMARC1 |
| Policy | p=invalid or p=block | p=none, p=quarantine, p=reject |
| Syntax | v=DMARC1 p=none (no semicolon) | v=DMARC1; p=none; |
| Email Format | [email protected] | rua=mailto:[email protected] |
CORRECTED DMARC RECORD EXAMPLE:
Case 3: Domain Mismatch
ERROR MESSAGE: "The sender email's domain doesn't match the selected sender domain. Please try a different email."
WHAT IT MEANS: Your 'From' email address uses a different domain than your selected sending domain.
EXAMPLE SCENARIO:
Sender Domain: inbox.yourdomain.com
From Email: [email protected]
Issue: luubu.com ≠ inbox.yourdomain.com
Solutions for Case 3
OPTION 1: Change From Email (Immediate)
Update your 'From' email to match your sending domain:
Wrong: [email protected]
Correct: [email protected]
OPTION 2: Use Your Own Authenticated Domain
If you have your own domain configured:
Select your authenticated domain as sender domain
Use matching email address (e.g., [email protected])
Ensure domain has proper SPF, DKIM, and DMARC setup
OPTION 3: Subdomain Strategy
Create aligned subdomains:
Sending Domain: mail.yourdomain.com
From Email: [email protected]
Benefit: Maintains brand consistency
Step-by-Step DNS Configuration
Follow these steps to add a DMARC record to your domain:
Step 1: Access Your DNS Provider
Log into your domain registrar or DNS hosting provider:
GoDaddy: Go to DNS Management
Cloudflare: Navigate to DNS tab
Namecheap: Access Advance