Send as your own domain
By default, tenants on a subdomain of a verified wildcard parent need no DNS at all (see Sending from a subdomain). Follow this guide when you want EmBoux to send email as your own root domain, for example example.com.
When you need it
Section titled “When you need it”- You want the visible sender to be an address of your own domain.
- Your domain is not a subdomain of a domain already verified in EmBoux.
Before you start
Section titled “Before you start”- Order matters. Register the domain in EmBoux first (verification generates its DKIM key), then publish the records in your DNS, and only when the domain shows as verified switch your application (Odoo) to send with it. Switching earlier gets your sends rejected (
550 5.7.1 Domain not verifiedor553 5.7.1 Sender domain is not enabled�). - If you already send volume (campaigns, newsletters): a new domain starts in the
standardwarm-up category, a ramp that begins at 50 emails/day and rejects anything above it. Ask for theestablishedcategory before your first send (see Warm-up Profiles). Your own domain also starts with its own, colder reputation: keep the first campaigns moderate and spread over time. - Keep your MX if your mailboxes stay with another provider; EmBoux only needs to send for the domain.
- Create the domain in EmBoux: in Odoo, Mailboxes > Domains > New, or
POST /domains/. - Start verification:
POST /domains/{domain}/verify. The response (and Odoo) show the exact DNS records to publish. - Publish the records at your DNS provider (below).
- Check them:
GET /domains/{domain}/dns-checkreports each record asok,missingorincorrect. - Activate:
PUT /domains/{domain}/activate. Activation provisions the sending credential automatically.
curl -X POST https://api.emboux.com/domains/ \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "example.com"}'
curl -X POST https://api.emboux.com/domains/example.com/verify \ -H "Authorization: Bearer YOUR_API_KEY"
curl https://api.emboux.com/domains/example.com/dns-check \ -H "Authorization: Bearer YOUR_API_KEY"
curl -X PUT https://api.emboux.com/domains/example.com/activate \ -H "Authorization: Bearer YOUR_API_KEY"DNS records
Section titled “DNS records”| Type | Name | Value |
|---|---|---|
| TXT (SPF) | example.com | v=spf1 include:emboux.com ~all |
| TXT (DKIM) | <selector>._domainkey.example.com | The value returned by /verify |
| CNAME | email.example.com | mailgun.org |
| MX (only if EmBoux receives your mail) | example.com | mx1.emboux.com (priority 10) |
Notes:
- SPF.
include:emboux.comis the canonical form and is whatdns-checkvalidates. Theinclude:mailgun.orgthat/verifyreturns is also valid, because the SPF ofemboux.comincludesmailgun.org. If your domain already has an SPF record, add the include to that record. Never publish two SPF records. - DKIM. Copy the selector and the public key exactly as returned by
/verify. - CNAME.
email.<domain>points tomailgun.org. - MX. Publish it only if EmBoux should receive the mail of that domain. If your mailboxes are with another provider (Google, Microsoft), do not change your MX.