Dedicated addresses
Route billing, support and reports to the workflow that owns them.
Maail Receive · InfrastructurePlanned
Turn incoming email into an event.
Give invoices, support and reports their own receiving routes. Send structured message data to your application.
What you can build
Inbound Email API & Signed Webhooks
Connect inboxes to your software. Explore the planned capabilities below.
Parsed content
Work with text, HTML, headers and message participants.
Attachments
Use bounded attachment access with explicit expiry and size limits.
Signed events
Authenticate each webhook and deduplicate by a stable event identifier.
Recoverable delivery
Retry failures, inspect delivery state and replay where authorised.
Retention controls
Set the message lifecycle separately from stateless analysis.
Three steps
A workflow your team can follow.
- Verify your receiving domain
- Create an address route
- Handle the signed event
In practice
Invoices enter your finance workflow
A supplier emails a dedicated address. Receive prepares the message; Extract can map the content to fields for your review queue.
Explore invoice extractionWhat is included in the wider product direction?
DMARC aggregate XML intake and report-specific normalisation extend the same receiving pipeline.
Do I need to replace the MX records for my main inbox?
Use a dedicated receiving subdomain when appropriate. It lets you route application mail separately from your existing mailbox provider; confirm the DNS setup during onboarding.
Can I integrate this product today?
This product scope is planned. Discuss your requirements with us to confirm available components, processing terms and integration timing. The public DNS tools can be used without an account.
Start with the task you want to simplify.
Tell us which messages, systems and decisions need to connect.