We're pleased to announce developers and agents can use their own domains for inbound processing in Paubox Email API.
In other words, you can point a domain you own at Paubox, create mailboxes on it, and have every message sent to those addresses delivered to your app via the API or webhooks.
Replies, referrals, and patient messages arrive on your brand’s domain, not ours, and stay HIPAA compliant from the moment they land.
See related: Receive emails with Paubox Email API
How does it work?
In the Paubox Dashboard, go to Settings => Domains. Click Add Domain, then toggle on Receiving. If a domain already receives email somewhere else, use a subdomain like inbound.example.com.
Next, setup your DNS records. You'll need to create or modify the following:
-
DKIM
- SPF
- MX
- DMARC (recommended)
How is encryption handled?
Inbound email must be sent using TLS 1.2 or 1.3 encryption. If no encrypted connection is offered, the message will not be accepted. If insecure protocols such as TLS 1.1, 1.0, SSL v2, or SSL v3 are used by the sender, the message will not be accepted.
See related: Paubox eliminates obsolete TLS protocols, follows NSA guidance
How much does it cost?
Each received email counts towards your Paubox Email API usage tier.
Is it HIPAA compliant?
Yes, the business associate agreement (BAA) you receive for Paubox Email API covers inbound email processing. In other words, it's a HIPAA compliant email solution.
