DEV Community

ReceiveHQ
ReceiveHQ

Posted on

One inbound domain, two webhooks: prod + staging without a second MX

#webhooks #saas #devops #europe

I'm Sebastian, CTO at ReceiveHQ (Cortena B.V.). Use-case #2: one inbound domain, multiple webhooks — prod + staging without a second MX.

The problem

You want the same mailbox on inbound.example.com in production and staging. Classic options (second MX, re-POST proxy, duplicated DNS) are awkward for GDPR-sensitive or Postmark-shaped parsers.

One parse, many deliveries

ReceiveHQ accepts SMTP, parses MIME once in Germany, then delivers per endpoint on the same domain:

  • prod → live HTTPS webhook (Postmark / Mailgun-SendGrid / CloudMailin shape)
  • staging → second HTTPS URL, independent retries/logs
  • optional blackhole → store-only for MCP/audit

Same MX (mx.receivehq.com). Same message. Separate attempt streams. Staging can 500 without poisoning prod.

Setup

  1. https://receivehq.com — magic-link sign-in
  2. Create domain, MX → mx.receivehq.com, verify
  3. Add two webhook endpoints (console or MCP create_inbound_domain_endpoint twice)
  4. Send a test; confirm both deliveries via console or list_deliveries

Docs: https://receivehq.com/mcp.md

Why this beats a re-post proxy

Parse once (14-day .eml retention). Independent backoff (1m→5m→30m→1h→2h) and HTTP 406 drop per endpoint. Drop-in payload shapes. EU residency on German Hetzner baremetal (Cortena B.V.).

Next: recipient filters so staging does not eat invoices@.

Try: https://receivehq.com · €10/mo or €100/yr · 100k inbound · first 10 free

Trust: hosting · DPA · sub-processors · imprint

Disclosure: I work on ReceiveHQ as CTO & Co-founder of Cortena B.V.

Top comments (0)