Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.keloa.ai/llms.txt

Use this file to discover all available pages before exploring further.

To send email from Keloa using your own domain (support@yourdomain.com), you have to prove you own that domain. This is standard email auth: a handful of DNS records at your DNS provider.

Add a domain

1

Open Email settings

Sidebar → SettingsChannelsEmailSet up, then Email domainsAdd domain.
2

Enter the domain

Just the domain — no @, no mailbox. E.g. yourdomain.com. Keloa registers it with Lettermint, our authenticated email provider.
3

Add DNS records

Keloa shows the records to add at your DNS provider. Each row has labels for Name and Content, plus a Copy button per field. The records typically include:
  • DKIM (TXT) — Lettermint’s signing key.
  • Bounce return path (CNAME) — points to Lettermint’s bounce handler.
  • DMARC (TXT) — alignment policy, starts permissive.
  • SPF (TXT) — optional, merged into your existing SPF if any.
  • Inbound MX (MX) — optional, only if this domain should also receive mail.
Click Setup guide for plain-language explanations of each record and a “Copy as zone file” option.
4

Wait for propagation

Usually 5 to 30 minutes. Some legacy providers take hours. Use dnschecker.org to watch propagation.
5

Verify

Back in Keloa, click Re-verify. Status flips to verified when all records resolve.
For per-record details, see DNS records.

Using the verified domain

Once verified, add an email channel — pick the visible mailbox you’ll reply as (e.g. support@yourdomain.com). Replies go out from there with your channel’s sender name and signature.

Plan limits

PlanDomains
Starter1
Growth3
Business10
ScaleUnlimited

Re-verifying

DNS records can drift (e.g. provider migration). Click Re-verify any time to re-check. If it fails, check your current records against what Keloa shows.

Removing a domain

⋯ → Remove. Any channels using this domain as sender will fall back to the default Keloa-branded sender until you pick another verified domain.

Troubleshooting

IssueFix
Verify keeps failingDNS not propagated yet, or record copied with a trailing .. Use the Copy button instead of selecting by hand.
SPF conflictYou already have an SPF record with a different provider. Merge them: one v=spf1 record with all include: entries.
Replies still in spamVerify DKIM — it’s the strongest signal. Also ensure your From name matches your brand, not a random username.
Gmail shows “via keloa.ai”Expected when only DKIM is set up but not a Return-Path alignment. Not harmful, and usually goes away after the bounce CNAME is right too.