Skip to content
nofeb

Get inbound email into an agent inbox

Mail reaches a nofeb inbox in one of two ways: a sending server delivers to nofeb's own MX, or a provider you already use forwards it with your organization's inbound token. Either way it goes through one pipeline, so the agent gets the same parsed message, the same events and the same wait_for_email.

Checked against the engine on .

The nofeb inbound pipeline Two entry points, nofeb's own MX and provider webhooks authenticated by an inbound token, feed the same pipeline: sender authentication and spam and virus checks at the MX, routing by envelope recipient, the inbound.resolve hook, an injection score, sender trust and typed decisions, then sender lists, the inbound.pre_deliver hook and rules, delivery to the inbox, Junk or quarantine, then a message.received event by webhook or event feed, and access over REST or MCP for the agent. Ways in nofeb MX Any mail server delivers STARTTLS offered Recipient checked at RCPT Provider webhooks Cloudflare Email RoutingPostmark inbound streamMailgun routeSendGrid Inbound ParseAny raw POST /v1/inbound/…/{token} At the door Checks before 250 OK SPF · DKIM · ARC · DMARC Spam and virus scan Refuse, accept, or Junk Pipeline One pipeline Route by envelope recipient Delivered once, even if resent inbound.resolve hook Scored and triaged injection score, sender trust decisions on every message sender lists inbound.pre_deliver hook rules quarantine, reject or file Parsed for the model reply_text · safe_body codes, links, attachments extracted metadata security verdict Inbox Agent inbox Inbox, Junk or quarantine Typed metadata on the thread Raw message kept byte-exact The agent hears message.received webhook, event feed or stream wait_for_email long-poll until it arrives Agent: REST, SDK or MCP
Mail from any sending server reaches nofeb's MX; mail already handled by Cloudflare Email Routing, Postmark, Mailgun or SendGrid is passed on with your inbound token. Both join the same pipeline, where each message is scored for injection, labelled and triaged before your sender lists, hooks and rules decide its fate, and the agent hears about it by webhook, the event feed, the stream, REST or MCP.

Which inbound paths are there?

PathHowTrust
nofeb MXPoint the domain's MX at nofebSender authentication, spam and virus checks at the door
Cloudflare Email RoutingEmail Routing with an Email WorkerOrganization inbound token, rotatable
PostmarkPostmark inbound streamOrganization inbound token, rotatable
MailgunMailgun inbound routeOrganization inbound token, rotatable
SendGridSendGrid Inbound ParseOrganization inbound token, rotatable
Raw POSTraw MIME webhookOrganization inbound token, rotatable

What does the agent do once mail arrives?

Get an inbox and wait for a code (TypeScript)
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.

CapabilityWhat it doesStatus
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