# Error: Sender domain not validated (Elastic Email)

Source: https://catalystgroup.gg/docs/email-delivery/error-elastic-email-domain-not-validated/
Updated: 2026-10-19 · By Duane Garner

Elastic Email will not send from a domain it has not verified. Add the DNS records it asks for, verify the domain, then test again.

> **Shown by the Elastic Email mailer:** The test result or the error log shows a message such as `Sender domain not validated` when CRM-NG SMTP sends through Elastic Email.

 

This article is for site owners using the **Elastic Email** mailer whose emails are refused because of the From address's domain.

 

## What this error means

 

Elastic Email only sends mail whose From address belongs to a domain you have proven you control. You prove it by publishing DNS records that Elastic Email gives you, then asking Elastic Email to check them. Until that check passes, any message with a From address on that domain is refused.

 

The domain checked is the part after the @ in **From Email** on **CRM-NG SMTP → Settings → General**. If another plugin changes the From address, that address is the one that counts.

 

## Common causes

 
- The domain was never added in Elastic Email.
- The domain was added, but the SPF or DKIM records were not published, or were published on the wrong host name.
- The records were published, but nobody pressed verify in Elastic Email afterwards.
- **From Email** uses a different domain from the one you verified, for example `example.net` instead of `example.com`, or a subdomain such as `mail.example.com`.
- Another plugin sets its own From address and **Force From Email** is off.
- DNS changes have not spread yet. This can take from minutes to a day.

 

## How to fix

 
1. Check the From address
  In **CRM-NG SMTP → Settings → General**, note the domain in **From Email**. Turn on **Force From Email** so other plugins cannot replace it.
2. Open the domains page in Elastic Email
  Sign in at `https://app.elasticemail.com/`, open **Settings** and choose **Domains**. If your domain is not listed, add it.
3. Copy the records
  Open the domain's verification details. Elastic Email lists an SPF record, a DKIM record and usually a tracking CNAME and a DMARC suggestion.
4. Publish them at your DNS host
  Add each record exactly as shown at the company that runs your domain's DNS. If you already have an SPF record, add Elastic Email's include to it rather than creating a second SPF record.
5. Verify in Elastic Email
  Return to the domain page and run the verification for each record. Wait until SPF and DKIM show as valid.
6. Send a test
  Go to **CRM-NG SMTP → Tools → Email Test**, enter an address in **Send To** and press **Send Email**.

 

## Verify it worked

 

The test page reports "Test email sent successfully! Check your inbox to confirm delivery." The test page also shows **Deliverability and domain authentication** results; the SPF line should say a record was found. In Elastic Email, the domain shows as verified and the test appears in the activity list.

 

## Notes

 
- On Elastic Email's free plan you can only send to your own account address, even with a verified domain. If you need to email customers, check your plan.
- You cannot verify a free mailbox domain such as `gmail.com` or `outlook.com`. Use an address on a domain you own.
- Two SPF records on one domain make both invalid. See [DNS records for email](https://catalystgroup.gg/docs/email-delivery/dns-records/).

 

## Related

 
- [Elastic Email mailer guide](https://catalystgroup.gg/docs/email-delivery/mailer-elastic-email/)
- [Sender name and address](https://catalystgroup.gg/docs/email-delivery/sender-name-and-address/)
- [Force From Email](https://catalystgroup.gg/docs/email-delivery/force-from-email/)
- [Verify your DNS records](https://catalystgroup.gg/docs/email-delivery/verify-dns-records/)
- [Troubleshooting email delivery](https://catalystgroup.gg/docs/email-delivery/troubleshooting/)