Which inbound paths are there?
| Path | How | Trust |
|---|---|---|
| nofeb MX | Point the domain's MX at nofeb | Sender authentication, spam and virus checks at the door |
| Cloudflare Email Routing | Email Routing with an Email Worker | Organization inbound token, rotatable |
| Postmark | Postmark inbound stream | Organization inbound token, rotatable |
| Mailgun | Mailgun inbound route | Organization inbound token, rotatable |
| SendGrid | SendGrid Inbound Parse | Organization inbound token, rotatable |
| Raw POST | raw MIME webhook | Organization inbound token, rotatable |
What does the agent do once mail arrives?
import { Nofeb } from "@nofeb/sdk";
const nf = new Nofeb(); // reads NOFEB_API_KEY
const inbox = await nf.inboxes.create({ local_part: "signup-bot", ttl_seconds: 3600 });
const since = new Date(); // before the form is submitted
// … type inbox.address into the sign-up form …
const { message } = await nf.inboxes.waitForEmail(inbox.id, { has_otp: true, timeout: 60, since });
const code = message?.otps[0]?.code; // "482913" Frequently asked questions
Which inbound path should I use?
If the domain's mail can move, point its MX at nofeb: you get sender authentication and spam and virus checks before acceptance, and a security verdict on every message. If the domain already receives through Cloudflare, Postmark, Mailgun or SendGrid, keep it and forward.
Does the path change what the agent sees?
No. Every path delivers raw MIME into the same pipeline, so reply_text, safe_body, codes, links, attachment text, threading and events are identical. Only mail received by nofeb's MX carries nofeb's own security verdict.
How is a forwarded message tied to the right inbox?
By the envelope recipient where the provider passes it, otherwise the To and Cc headers. Only your organization's inboxes and verified domains can receive through your token.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| 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 |
| 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 |
| Raw message push | Push raw MIME into any of your inboxes for imports and generic inbound webhooks. | Shipped |
| Wait for an email | Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. | Shipped |
| Signed webhooks with required scope | Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. | Shipped |