Custom domains and DNS

A custom domain receives test mail on a hostname you control. Custom domains are available on Team, Business, and Enterprise. Free and Developer use the assigned domain only. Mail is accepted after both DNS records are in place and verification succeeds. Until then the domain stays pending and senders are refused.

Create the domain

devhelm email domains create --name mail-test.example.com

curl -X POST "https://api.devhelm.io/api/v1/email/domains" \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN" \
  -H "x-phelm-workspace-id: $DEVHELM_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{"kind":"custom","name":"mail-test.example.com"}'

Use a subdomain you do not send real mail from. Its MX record will point at DevHelm.

Publish DNS

Add both records at your DNS provider. The verification token is on the domain; devhelm email domains get prints the records.

Type	Host	Value
TXT	`_devhelm-verification.mail-test.example.com`	`devhelm-verification=<token>`
MX	`mail-test.example.com`	`mx.devhelmmail.com` (priority 10)

devhelm email domains get mail-test.example.com

Verify

devhelm email domains verify mail-test.example.com

curl -X POST "https://api.devhelm.io/api/v1/email/domains/mail-test.example.com/verify" \
  -H "Authorization: Bearer $DEVHELM_API_TOKEN" \
  -H "x-phelm-workspace-id: $DEVHELM_WORKSPACE_ID"

When both records resolve, the domain becomes active and any address on it can receive mail. DNS changes can take a few minutes to show up. Leave the records in place after verification.

Getting Started

Webhook testing

Monitoring as Code

Monitoring

Incidents

Alerting

Status Data

Email testing

Platform

Common Patterns

Custom domains and DNS

Create the domain

Publish DNS

Verify

Next steps

How capture works

Wait for an email

​Create the domain

​Publish DNS

​Verify

​Next steps

How capture works

Wait for an email

Create the domain

Publish DNS

Verify

Next steps