Domain & authorized senders
Domain setup
Domain & authorized senders
Start here: E-mail — documentation hub.
Before Routee accepts a transactional email (HTTP or SMTP), your sending domain must be verified and your From address must be an authorized sender on that domain.
Configure everything under Email → Domains on go.routee.net.
Why domain verification matters
| Reason | Detail |
|---|---|
| Deliverability | SPF and DKIM prove Routee is allowed to sign and send on your behalf. |
| Trust | Recipients and mailbox providers treat unauthenticated mail as suspicious. |
| Policy | Routee rejects sends from unverified domains or unauthorized senders at the API/SMTP layer. |
Step 1 — Add a domain
- Open Email → Domains → Add domain.
- Enter the domain you will use in
Fromaddresses (e.g.yourdomain.com). - Routee generates SPF and DKIM DNS records for that domain.
Step 2 — Publish DNS records
SPF
Include Routee in your SPF record so receiving MTAs accept mail from our infrastructure:
v=spf1 mx include:email.routee.net ~allMerge with your existing SPF if you already have one — only one SPF TXT record per domain is allowed.
DKIM
Add the TXT record Routee provides, typically:
| Type | Host / name | Value |
|---|---|---|
| TXT | routee._domainkey.yourdomain.com | Public key from the portal (RSA) |
Routee signs outbound mail with selector routee. Receiving servers fetch this public key to verify signatures.
Optional — DMARC
After SPF and DKIM work, consider a DMARC policy on _dmarc.yourdomain.com to monitor or enforce alignment. Routee docs do not require DMARC for verification, but it improves deliverability monitoring.
Step 3 — Verify the domain
- Wait for DNS propagation (minutes to 48 hours depending on TTL).
- Click Verify on the domain row in the portal.
- Status changes to Verified when SPF and DKIM checks pass.
Until verified, sends using @yourdomain.com addresses are rejected.
Step 4 — Authorized senders
Each From address must be explicitly authorized:
- On the domain detail page, open Authorized senders.
- Add an email address (e.g.
[email protected]). - Routee sends an invitation email with a personalized link (valid 72 hours).
- The recipient clicks the link → status becomes Verified.
You can resend the invitation if it expires. At least one verified sender is required before the account can send.
Portal checklist
| Step | Portal location | Done when |
|---|---|---|
| Add domain | Email → Domains | Domain row exists |
| SPF in DNS | Your DNS provider | include:email.routee.net present |
| DKIM in DNS | Your DNS provider | routee._domainkey TXT published |
| Verify domain | Domain → Verify | Status Verified |
| Add sender | Domain → Authorized senders | Address listed |
| Confirm sender | Invitation email link | Sender Verified |
Common rejection reasons
| Symptom | Likely cause |
|---|---|
HTTP 400 000000 | Domain not verified or SPF/DKIM missing |
HTTP 400 000001 | Invalid sender address format |
HTTP 400 000002 | Sender not authorized / not verified |
SMTP reject at MAIL FROM | Same — domain or sender not allowed |
See Send a transactional email for the full HTTP error code table.
SMTP credentials (after setup)
Once domain and sender are ready, use Connect application credentials for SMTP:
- Host:
smtp10.amdtelecom.net - Username / password: Application Id / Application Secret
Guide: Transactional Email — SMTP relay

