Setup
Domains
The DNS records emitemail asks for and why each one matters.
You can only send from domains you have proven you control. Under Domains, add a domain and emitemail shows the records to publish. Replace yourstore.com below with your own.
| Type | Host | Purpose |
|---|---|---|
| CNAME | emit._domainkey.yourstore.com |
DKIM. Lets receivers check that the message really came through emitemail for your domain. The value is unique to your domain, which also proves ownership. |
| TXT | yourstore.com |
SPF. Says emitemail is allowed to send for your domain: v=spf1 include:emit.xenkloud.com ~all |
| TXT | _dmarc.yourstore.com |
DMARC. Tells receivers what to do with mail that fails the checks. Starts at p=none, which only reports. |
Click Verify after publishing. DNS changes can take minutes to hours to be visible.
A domain may have only one SPF record. If you already have one, do not add a second. Merge emitemail into it, for example v=spf1 include:_spf.google.com include:emit.xenkloud.com ~all.
If a record goes missing later#
If a record that was verified disappears, the domain moves to needs attention. Sending keeps working so a DNS slip does not break your app without warning, and the dashboard tells you what to fix.
Tightening DMARC#
p=none is a safe start. Once your DMARC reports look clean, move to p=quarantine and later p=reject to stop others from spoofing your domain.
Which address to send from#
Use an address on a verified domain, for example orders@yourstore.com. An API key can also be limited to a single domain, so a leaked key cannot send as your other domains.