The email half of the receiver. Signature and freshness are checked, the real author is taken from the From header rather than the envelope, and the account is resolved by a VERP address first and a uniquely-owned domain second. A domain shared by more than one account returns 'ambiguous' and the message is held.
Also called: email reply routing · reply went to the wrong company · shared email domain · inbound email
- 1HMAC-SHA256 of (timestamp + token), with a 15-minute freshness window so a captured request is not replayable forever
- 2reply+{account}@domain wins outright; otherwise the domain must belong to exactly ONE account
- 3More than one owner returns ambiguous with the count, and the message is stored unrouted
- 4The From header is preferred over the envelope sender, which legitimately differs for forwarders and relays
Several businesses share one sending domain, and the original approach filed a reply to the first account that looked like a match — which can put one builder's customer reply into a competitor's inbox. Holding a message for a human to place is recoverable; misfiling it is not. Inbound email is verified and filed to an account only when the address identifies one beyond doubt, and held for triage rather than guessed at when it does not.
- Cross-account misfiling of customer replies
- Replies lost on a fallback provider
- Replayable webhook requests
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 →