Talk to our team

Documentation

✉️ Email Delivery

Documentation, reference material and tutorials for CRM-NG SMTP Email: setup guides for every mail service, troubleshooting, and one article per error message.

Error: Domain not verified (MailerSend)

Updated

By Duane GarnerChief Executive Officer (CEO)
Summarize: Claude ChatGPT View Markdown
On this page

MailerSend will not send from a domain it has not verified. Add the domain's DNS records, verify them, and send from that domain.

This article is for sites using the MailerSend mailer where a send fails because the From address's domain is not verified.

The error as you see it

The from.email domain must be verified in your account to send emails. (shown with a code starting with #MS, and in the log as "domain not verified")

Shown by the MailerSend mailer, in the failed-send banner, in Tools → Debug Events and in the Email Log. MailerSend returns it with HTTP status 422.

What this error means

MailerSend only sends from domains you have added to your account and proved you own with DNS records. The domain it checks is the part of your From Email after the @. Your API key is fine; the domain is either not in your MailerSend account, or its records have not been confirmed.

Common causes

  • The domain was never added to MailerSend, or was added in another MailerSend account.
  • The DNS records are missing or wrong. MailerSend needs its SPF and DKIM records (and usually a return-path CNAME) before it marks the domain verified.
  • DNS has not spread yet. New records can take from minutes to a day or two to be visible everywhere.
  • The From Email uses a different domain or subdomain than the one you verified, for example example.com against mail.example.com.
  • Another plugin changes the From address to something like wordpress@yoursite because Force From Email is off.
  • The API key is tied to a different domain. MailerSend keys can be limited to certain domains.

How to fix

  1. See which domain was used

    Check the From of the failed email in CRM-NG SMTP → Settings → Email Log, or the From Email on CRM-NG SMTP → Settings → General.

  2. Open your domains

    Sign in to https://app.mailersend.com/ and go to Domains. If the domain is missing, choose Add domain and enter it.

  3. Add the DNS records

    Open the domain and copy each record it lists into your DNS host. Enter the name without repeating your domain if your DNS host adds it automatically. For Cloudflare, set CNAME records to DNS only.

  4. Verify

    Back on the domain page in MailerSend, press the verify or check button. Repeat after some time if records are still missing.

  5. Check the API key's scope

    Under the domain's API settings, or the API tokens page, make sure the key used by your site may send for this domain. If not, create a new token with sending access for the domain.

  6. Update CRM-NG SMTP

    In CRM-NG SMTP → Settings → General, set From Email to an address on the verified domain and tick Force From Email. If you made a new token, use Remove API Key and paste it into API Key. Press Save Settings.

  7. Send a test

    Go to CRM-NG SMTP → Tools → Email Test, fill in Send To and press Send Email.

Verify it worked

MailerSend shows the domain as verified, and the test page reports "Test email sent successfully! Check your inbox to confirm delivery." The "Deliverability and domain authentication" section of the test page should find your SPF record.

Notes

Go to Top