Skip to content
nofeb

Product / Sending and delivery

Delivery from your own domains

Deliverability is where agent mail goes wrong: a shared domain, one bad sender, and everyone's mail lands in spam. nofeb delivers from your own domains with authentication set up for you, ramps new domains up gently, stops sending before a bad run does lasting damage, and keeps each customer's sending reputation apart rather than pooled.

Sending, replying and forwarding

Send from any inbox, reply in-thread with the threading headers set for you, reply-all, or forward with the original attachments. Give a send a send_at time to schedule it. Send the same Idempotency-Key twice and it goes out once, which matters when the caller is an agent that retries.

Mail between inboxes on the platform is delivered internally, which makes agent-to-agent workflows and test environments cheap and fast.

Nothing to run

You run no mail servers and manage no sending IPs. Outbound mail leaves from your verified domain, signed with DKIM, with a custom MAIL FROM so SPF and DMARC align, and nofeb handles the delivery.

Two ways to send

  • Managed, the default. nofeb sends on your behalf from your verified domain. Each organization can send with its own isolated reputation, so one sender's behaviour cannot damage another's.
  • Bring your own Amazon SES. Grant nofeb an IAM role in your own AWS account and mail goes out through your SES, on your reputation, limits and bill. The API accepts the role and sends through it; verification against live customer accounts is still in progress. Beta

Warm-up and automatic pausing

A new managed domain follows a warm-up schedule: a cap on external recipients per day that rises each day after verification. Sends over the day's cap wait for the next day; none is dropped. Change the schedule or switch it off per domain.

If an organization's permanent-bounce or complaint rate over the evaluation window crosses its threshold, outbound sending pauses on its own and sending.paused says why. New external sends are refused with sending_paused while queued ones wait, until you resume by API or in the console, which releases them. Every inbox also has a default brake on first contact, the number of new people it may write to a day, unless your own caps say otherwise.

Sending health
GET  /v1/sending
GET  /v1/domains/{domain_id}/warmup
POST /v1/sending/resume

Your domains

Add a domain and nofeb returns the DNS records to publish: DKIM, a custom MAIL FROM and a DMARC policy, plus the inbound MX if you want nofeb to receive the domain's mail. It checks them, and emits domain.verified when they pass.

Inboxes can also use the shared nofeb domain, where sponsor gating limits new organizations to replies until a human verifies.

DNS without the support ticket

Most failed domain setups are a record typed into the wrong box, such as a name with the domain appended twice. nofeb looks up who hosts the domain's DNS and returns the shortest path for that host, with a live check of every record that shows what was found and what is likely wrong.

  • Published for you. On Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun and Gandi, hand nofeb an API token for one call and it creates the records. The token is never stored and nothing is deleted; a conflict it will not resolve on its own, such as another SPF record at the same name, comes back with what to do.
  • Instructions for every other host. Step-by-step instructions in the detected host's own terms with a link to its DNS console, plus a zone file, a Route 53 change batch and Terraform, to apply the records your own way.
  • Receiving is a separate choice. Pointing the domain's MX at nofeb is its own step, so publishing sending records never moves where your mail is delivered.
  • One click with Domain Connect. At DNS hosts that support Domain Connect, nofeb builds a signed link where you sign in, review the records and click Connect. The link appears for a host once that host has adopted nofeb's template. Beta
Find the easiest way to publish
GET /v1/domains/{domain_id}/dns-setup

{ "provider_label": "Cloudflare",
  "api": { "supported": true, "endpoint": "/v1/domains/{domain_id}/dns/apply" },
  "instructions": [ ... ],
  "exports": { "zone_file": "...", "route53_change_batch": { ... }, "terraform": "..." },
  "records": [ ... ] }

POST /v1/domains/{domain_id}/dns/apply
{ "credentials": { "provider": "cloudflare", "api_token": "..." } }
Publishing email DNS records Add a domain; nofeb detects the DNS host from its NS records. Then one of three paths: a one-click Domain Connect link (Beta), publishing through the host's API with a token used once (Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun, Gandi), or instructions written for that host plus zone-file, Route 53 and Terraform exports. Every record is then checked live, showing what was found and the likely mistake, and domain.verified is emitted when all pass. Add the domain POST /v1/domains records generated Detect the DNS host from its nameservers GET …/dns-setup One-click Domain Connect sign in at the host, click Connect Beta Published through the API token used for one call, never stored POST …/dns/apply Instructions for that host host and value boxes, as its form wants zone file · Route 53 · Terraform Live check found value and likely fix domain.verified
nofeb looks up who runs the domain's DNS from its nameservers, takes the shortest path that host allows, then checks every record live until domain.verified fires.

Saying an agent wrote it

Turn on AI disclosure for an organization, a pod or one inbox, and mail its agents send carries AI-Generated and AI-Disclosure headers, with an optional footer in the text and HTML bodies, added after your outbound hooks have run. Mail a person sends from the console or the webmail never carries it, and one inbox can be exempted from an organization-wide setting. Changing it needs a policy scope that agent keys do not hold.

Disclose for the whole organization
PUT /v1/ai-disclosure
{ "scope": "org", "enabled": true,
  "footer_text": "This message was written by an AI assistant." }

What happens after a send

Delivery, bounce and complaint reports come back as message.delivered, message.bounced and message.complained events, naming the inbox and thread. A recipient who hard-bounces or complains is suppressed automatically, so an agent that retries cannot keep mailing them.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Send, reply, reply-all and forward Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Shipped
Scheduled send Give any send a future send_at time. Shipped
Idempotent sends Retry a send with the same Idempotency-Key and it is sent once. Shipped
Delivery between inboxes Mail between inboxes on the platform is delivered internally, for agent-to-agent workflows and test environments. Shipped
Managed outbound delivery nofeb delivers your outbound mail from your verified domains, signed with DKIM and aligned for SPF and DMARC. There are no mail servers or sending IPs for you to run. Shipped
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped
One-click DNS with Domain Connect At DNS hosts that support Domain Connect, a signed link where you sign in to your DNS host, review the records and click Connect. The engine builds and signs the link; it appears for a host only once that host has adopted nofeb's published template. Beta
Managed sending with per-tenant reputation isolation nofeb sends on your behalf from your verified domain, and each organization can send with its own isolated reputation, so one sender's behaviour cannot damage another's. Shipped
Automatic pausing and warm-up New custom domains follow a daily warm-up ramp; sends over the day's cap wait for the next day instead of being dropped. If an organization's bounce or complaint rate crosses its threshold, sending pauses automatically and an event says so; resume it by API or in the console. First contact per inbox is throttled by default. Shipped
Delivery events and automatic suppression Delivery, bounce and complaint reports arrive as events, and hard-bounced or complaining recipients are suppressed automatically. Shipped
AI-generated disclosure Per organization, pod or inbox, mail an agent sends carries AI-Generated and AI-Disclosure headers and an optional footer. Mail a person sends from the console or the webmail never does. Shipped
Bring your own Amazon SES account Send through your own Amazon SES account by granting nofeb an IAM role; the API accepts the role and sends through it, and verification against live customer accounts is still in progress. Beta