Salesforce7 min read

Australian Salesforce Users: The April 27 Email Domain Verification Deadline

A critical security update is flying under the radar—and it could devastate customer relationships if you're not prepared. Domain verification now required for all Salesforce emails in Australia.

Robin Leonard
Robin Leonard
22 March 2026
Australian Salesforce Users: The April 27 Email Domain Verification Deadline

A critical security update is flying under the radar—and it could devastate customer relationships if you're not prepared. Domain verification now required for all Salesforce emails.

If your Australian organization sends emails through Salesforce and you haven't implemented domain verification, you have less than 30 days to avoid catastrophic email deliverability issues.

Starting April 27, 2026, emails from unverified domains will be rejected by major email providers, including Gmail, Outlook, and corporate email systems across Australia.

What's Happening

Australian organizations must verify ownership of their email domains in Salesforce before April 27, 2026. This includes:

- Sales emails sent from Salesforce
- Marketing Cloud campaigns
- Service Cloud automated responses
- Custom email templates
- Workflow email alerts

Non-compliance means your emails won't be delivered.

Why This Matters Now

Email Authentication Standards

Australian ISPs and corporate email providers are enforcing stricter authentication requirements to combat email fraud and phishing attacks.

Immediate Business Impact

- Customer communications will fail silently - Sales follow-up emails will bounce - Marketing campaigns will have zero deliverability - Service case notifications won't reach customers - Password reset emails won't work

Reputational Risk

Your domain reputation will be permanently damaged if you send emails after the deadline without proper verification.

Required Actions

1. Audit Your Email Domains

Identify every domain used for Salesforce emails: - Primary company domain - Department-specific domains - Regional office domains - Subsidiary company domains - Temporary campaign domains

2. Implement DKIM Authentication

Set up DomainKeys Identified Mail (DKIM) for each domain: - Generate DKIM keys in Salesforce - Add DKIM records to your DNS - Verify authentication is working - Test email delivery

3. Configure SPF Records

Update Sender Policy Framework (SPF) records: - Include Salesforce sending servers - Update existing SPF records - Avoid exceeding DNS lookup limits - Test SPF validation

4. Set Up DMARC Policies

Implement Domain-based Message Authentication: - Start with monitoring mode (p=none) - Analyze DMARC reports - Gradually increase policy strictness - Monitor for delivery issues

Step-by-Step Implementation

Phase 1: Domain Inventory (Complete by March 31)

Example: Audit Email Domains ```sql SELECT Domain_c, EmailType_c, Statusc FROM EmailDomainInventoryc WHERE Countryc = 'Australia' ```

Phase 2: DKIM Setup (Complete by April 10)

1

Navigate to Setup → Email Administration → Deliverability

2

Add each domain requiring verification

3

Generate DKIM keys for each domain

4

Work with IT team to add DNS records

5

Verify DKIM authentication

Phase 3: SPF Configuration (Complete by April 15)

Example SPF Record for Salesforce: ```dns v=spf1 include:
spf.salesforce.com include:salesforce.com ~all ```

Phase 4: DMARC Implementation (Complete by April 20)

Example DMARC Record (Start with Monitoring): ```dns v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com.au ```

Phase 5: Testing & Validation (Complete by April 25)

- Send test emails from each verified domain - Verify delivery to major email providers - Check DMARC reports for authentication failures - Document any remaining issues

Common Pitfalls

Incomplete Domain Inventory

Many organizations forget about: - Sandbox domain configurations - Legacy email addresses still in use - Third-party application integrations - Department-specific email domains

DNS Propagation Delays

DNS changes can take 24-48 hours to propagate globally. Start early to avoid last-minute issues.

Testing in Production Only

Test domain verification in sandbox environments first, but remember that production DNS changes are separate.

If You Miss the Deadline

Immediate Actions:



1


Stop all Salesforce email sending






2


Communicate with customers about delivery issues






3


Implement domain verification immediately






4


Monitor domain reputation recovery



Recovery Timeline:
- Domain verification: 1-2 days
- Reputation recovery: 2-4 weeks
- Full deliverability restoration: 4-8 weeks

Getting Help

If you're not confident about implementing domain verification:

Internal Resources:
- IT/Network administration team
- Salesforce administrators
- Email marketing specialists

External Support:
- Salesforce partners with email expertise
- DNS/email delivery consultants
- Marketing Cloud specialists

Don't Risk Your Email Communications

Email is the lifeline of modern business communication. A few days of preparation now can prevent weeks of communication chaos and permanent reputation damage.

Start your domain verification today. Your customers, sales team, and business operations depend on it.

Robin Leonard

About Robin Leonard

Partner at Xenai Digital and APAC's leading enterprise Salesforce consultant with 500+ enterprise transformations.

Share this article:
Topics:Email SecurityDomain VerificationAustraliaComplianceBusiness Continuity

Enjoyed This Article?

Get weekly enterprise AI insights like this delivered to your inbox. Real strategies from 500+ Salesforce transformations across APAC.

Join 15,000+ enterprise leaders • No spam • Unsubscribe anytime

Ready to Apply These Insights to Your Enterprise?

Let's discuss how these strategies can transform your specific challenges into competitive advantages.

Explore more enterprise insights: