Receive email
Native inbound is implemented but deployment-gated. Do not publish an MX record until the selected regional deployment reports receiving as enabled and ready.
Not generally available. The Sydney deployment’s receiving path must be enabled and operationally verified before use.
When enabled
Add a receiving domain. Create a domain with receiving enabled, preferably a dedicated subdomain such as replies.acme.com.
Publish its MX record. Add only the MX record returned by a deployment that reports receiving ready.
Create a webhook. Subscribe to email.received to receive signed inbound events.
Build for reliable delivery
Verify each webhook against its raw body before parsing it, acknowledge after durable enqueueing, and deduplicate with event.id. Fetch the message from the regional API when you need its full content or attachments.
curl https://api.au.boundry.dev/emails/receiving \
-H "Authorization: Bearer $BOUNDRY_API_KEY"