How does Envelope recipient work?
Headers are part of the message content and anyone can write anything in them. The envelope is set by the delivering server for this delivery. A system that routes by the To: header can be tricked into filing a message in the wrong mailbox; one that routes by the envelope cannot.
Webhook-based inbound services pass the envelope separately when they can; when the envelope is missing, the headers are the only clue.
How does nofeb use Envelope recipient?
- nofeb delivers to the inbox named in the envelope on every path that carries it: its own MX, the Cloudflare Email Worker and the raw POST endpoint's
toparameter. Redelivering the same message is idempotent. - Per-tenant isolation follows from it: a message can only land in an inbox its envelope names, and a provider token can only deliver to its own organization's inboxes.
Frequently asked questions
Why did a Bcc'd message arrive without my address in To:?
Because Bcc recipients exist only in the envelope. Routing by envelope is what delivers it to the right inbox.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Inbound routed by envelope recipient | Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. | Shipped |
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |
| Inbound from the provider you already use | Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. | Shipped |