A direct-send adapter driven by the account's binding: domain, API key and From identity, with an optional per-stream domain map and a regional base URL. Open and click tracking are switched on for every message. A neutral shared root is used for accounts that have not set up their own domain yet.
Also called: Mailgun · send from my company domain · SPF DKIM · email deliverability
- 1The registry resolves the account's Mailgun binding and decrypts the API key.
- 2The sending domain is chosen: stream domain, then binding domain, then the shared tenant root.
- 3The message posts to the Mailgun messages endpoint with a 15-second timeout.
- 4Tracking flags are set so the events webhook can report delivered, opened and clicked.
- 5A rejection is non-retryable; a network exception is retryable and enqueued.
The catalogue blurb states the builder-facing reason: 'Send from your own domain, so replies come back to you and your mail lands in the inbox.' The adapter carries a hard multi-tenant rule (Keith 08-10): the shared root 'is the NEUTRAL SHARED ROOT for sub-accounts that haven't set up their own sending domain — tenant mail must never ride the agency's own domain.' The inverse is enforced too: a platform-level send with no binding is refused rather than relabelled, because 'quietly relabelling it as pfbuild.com would put the agency's invitations, billing and notifications on a domain Keith doesn't send business mail from — silently, and pooled with every tenant's reputation.' Tracking is Keith 08-19.
- Mail sent from a shared or vendor domain damaged deliverability and looked unprofessional.
- Tenant mail riding the agency domain pooled reputations across unrelated businesses.
- Platform mail could have been silently relabelled onto the tenant domain.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →