Skip to content
nofeb

Forward your email to an AI agent

Create a forwarding address on the agent's inbox with POST /v1/inboxes/{inbox_id}/forwarding-addresses, naming the person and the mailboxes they forward from. Point their Gmail or Outlook forwarding at the fwd-… address. nofeb recognises the provider's confirmation email and puts its code and link on the address and on a forward.confirmation event, then delivers each forwarded message with the original sender and signatures intact.

Checked against the engine on .

What do you need?

  • An inbox the agent reads
  • The person's mailbox, with permission to set up forwarding or a mail rule

Steps

  1. 1. Create the address

    allowed_senders lists the mailboxes the person forwards from; it defaults to their own address. Mail that cannot be traced to one of them is refused and reported as message.rejected, so a leaked forwarding address is not an open door into the agent.

    A forwarding address for one person
    curl -X POST https://api.nofeb.com/v1/inboxes/inb_…/forwarding-addresses -H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \
      -d '{"person_email": "dana@example.com", "label": "Dana", "allowed_senders": ["dana@example.com", "dana@example.org"]}'
    
    { "id": "fwd_…", "address": "fwd-…@…", "person_email": "dana@example.com", … }
  2. 2. Set up forwarding at the provider

    In Gmail, add the address under forwarding settings; in Outlook, add a forwarding rule; or forward single messages by hand. Gmail and Outlook first send a confirmation message to the new address.

  3. 3. Complete the confirmation without reading the inbox

    nofeb recognises the confirmation, and its code and link appear on the forwarding address (GET /v1/forwarding-addresses/{forward_id}, field confirmation), in the message's metadata and on a forward.confirmation event. Your app shows the code to the person, or the agent opens the link, and forwarding starts.

  4. 4. Read what arrives

    Forwarded mail is delivered byte for byte with the original sender, DKIM and ARC preserved, and tagged with forwarded_by, forward_kind (auto, manual or confirmation), how it arrived and, for a message forwarded by hand, original_from. The receive-time SPF, DKIM, ARC and DMARC results are attached, so the agent can tell what the original sender actually proved.

How does nofeb know a message came from the person?

It looks for the traces automatic forwarding leaves: the envelope sender, including Gmail's rewritten form, the X-Forwarded-For and Exchange inbox-rule headers, Resent-From, or for a manual forward the From of the forwarding message, authenticated when it reaches nofeb's own MX. A message that matches none of the allowed senders is dropped.

Rotating an address issues a new one and stops the old one at once, which needs the person to update and re-confirm their forwarding. Revoking it refuses mail to it from then on.

Frequently asked questions

How do I forward my email to an AI agent?

Create a nofeb forwarding address on the agent's inbox, add it as a forwarding address in Gmail or Outlook, and confirm with the code nofeb surfaces. From then on your forwarded mail lands in the agent's inbox.

Can someone else send mail to my forwarding address?

They can try, but each address accepts only mail traceable to the senders you allowed; anything else is refused and reported.

Does the agent see the original sender?

Yes. Automatic forwards keep the original message byte for byte, and manual forwards record the original sender in original_from.

Status of everything on this page

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

CapabilityWhat it doesStatus
Forward to an agent Per-person forwarding addresses that bring someone's own mail into their agent's inbox byte for byte, accepting only mail traceable to the senders you allow. Gmail and Outlook forwarding-confirmation codes and links are recognised and surfaced, and each address can be rotated or revoked. 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
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped