MailSimple guide — November 2026 · 5-minute read · you'll never have to do this by hand with us, but understanding always helps
To receive email on your domain, 4 types of DNS records must be set correctly. This is the part where 9 out of 10 people trying to set up custom email give up. Here's each one in human language.
The MX record tells the world: "email for mydomain.ca goes to that machine." It's your mailbox's postal address.
Example: mydomain.ca → MX 10 mail.mailsimple.ca
The SPF record lists the servers allowed to send mail on your behalf. Without it, a spammer can pretend to write as you — and Gmail trusts you less quickly.
Example: v=spf1 include:mailsimple.ca -all
Every outgoing email is signed with a private key; DKIM publishes the public key. The receiving server checks the signature — proof the message came from you and wasn't altered in transit.
Example: mail._domainkey → TXT v=DKIM1; k=rsa; p=MIIB…
DMARC tells receiving servers what to do when SPF or DKIM fails (reject, quarantine), and sends you reports. It's the belt and the suspenders.
Example: _dmarc → v=DMARC1; p=quarantine; rua=mailto:dmarc@…
Since 2024, Gmail and Yahoo require SPF + DKIM (+ DMARC for bulk senders). A misconfigured domain = your emails in spam, or rejected outright. This isn't cosmetic — it's whether your messages get delivered.
With MailSimple, you touch none of this. Domain on Cloudflare → we set all 4 records automatically via the API, in about 2 minutes. Domain elsewhere (GoDaddy, Namecheap, CanSpace…) → our assistant shows you exactly what to copy-paste. That is the product.
I already have a website on my domain — will email break it? No — email records (MX etc.) and website records (A/CNAME) coexist without issues.
How long until it works? DNS propagates in 5 minutes to a few hours depending on the registrar.
What if I make a mistake? With us, it's impossible — it's automated. Elsewhere, a wrong record is fixed by simply editing it again.