What do you need?
- A nofeb key with key:manage, to create the app password
- A mail client, a tool with an IMAP/SMTP connector, or a language with IMAP and SMTP libraries
Steps
-
1. Create an app password
An app password belongs to one inbox and one client: it has a name, it is shown once, and it never carries more scopes than the key that created it (by default inbox:read, message:read, message:write and message:send). Creating one is deliberately not an MCP tool, so an agent cannot mint credentials for itself.
One password for one client curl -X POST https://api.nofeb.com/v1/inboxes/inb_…/app-passwords -H "Authorization: Bearer $NOFEB_ADMIN_KEY" \ -H 'content-type: application/json' -d '{"name": "SDR tool connector"}' -
2. Read the connection settings
The response to creating the password includes them, and GET /v1/inboxes/{inbox_id}/mail-client-settings (the get_mail_client_settings tool) returns them at any time. Logins work only over TLS, and repeated failed logins from one address are throttled across all three protocols.
Mail client settings { "username": "quotes@agents.example.com", "imap": { "host": "imap.nofeb.com", "port": 993, "security": "tls", "starttls_port": 143 }, "pop3": { "host": "pop.nofeb.com", "port": 995, "security": "tls", "starttls_port": 110 }, "smtp": { "host": "smtp.nofeb.com", "port": 465, "security": "tls", "starttls_port": 587 }, "auth": ["PLAIN", "LOGIN", "OAUTHBEARER", "XOAUTH2"] } -
3. Read over IMAP
The server speaks IMAP4rev2 with IMAP4rev1 compatibility, so standard libraries work unchanged. IDLE wakes on new mail, and CONDSTORE and QRESYNC let a client resync without downloading everything again. Flags you set over IMAP are the same keywords the API and MCP see.
Python: unread mail import imaplib, os imap = imaplib.IMAP4_SSL("imap.nofeb.com", 993) imap.login("quotes@agents.example.com", os.environ["NOFEB_APP_PASSWORD"]) imap.select("INBOX") _, data = imap.uid("SEARCH", None, "UNSEEN") for uid in data[0].split(): _, msg = imap.uid("FETCH", uid, "(RFC822)") -
4. Send over SMTP submission
The envelope sender must be an inbox the credential covers and the From header must match it. The message is filed in Sent and sent as composed, with Bcc taken from the envelope and stripped from the headers. If the inbox's policy holds it, the server still accepts it and says so:
250 … queued as snd_… (held for approval).Python: send import smtplib, os from email.message import EmailMessage msg = EmailMessage() msg["From"] = "quotes@agents.example.com" msg["To"] = "buyer@example.com" msg["Subject"] = "Your quote" msg.set_content("Attached is the quote we discussed.") with smtplib.SMTP_SSL("smtp.nofeb.com", 465) as s: s.login("quotes@agents.example.com", os.environ["NOFEB_APP_PASSWORD"]) s.send_message(msg)
Why would an agent use IMAP when there is an API?
Many tools only speak mail protocols: SDR platforms with an IMAP/SMTP mailbox connector, helpdesks that poll a mailbox, older automation and every desktop client. Pointing them at a nofeb inbox gives them an address you created by API, with keys you can scope and revoke, while nofeb still enforces the sending policy they know nothing about.
POP3 covers the Inbox only, with UIDL and TOP; deleting a message takes effect when the session ends. Appending to Sent over IMAP never sends anything, and appending to Drafts files a draft that the API, JMAP and the webmail see.
Frequently asked questions
Can I connect an AI agent's inbox to Thunderbird or Apple Mail?
Yes. Use the inbox address as the username, an app password as the password, and the hosts and ports from the mail client settings.
Does SMTP bypass the approval tier?
No. A submitted message goes through the same policy as an API send, and a credential that holds send:approve does not make its own submission approved.
What happens when I revoke an app password?
New logins with it fail at once. Sessions already open end when they log out or go idle: 30 minutes for IMAP, 10 for POP3.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| IMAP and POP3 | IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. | Shipped |
| SMTP submission | Authenticated SMTP submission on ports 587 and 465 for tools that only speak SMTP. Every submitted message meets the same autonomy tiers, approvals, lists, caps and hooks as an API send, and a held message is accepted and reported as held. | Shipped |
| Autonomy tiers enforced by the server | Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. | Shipped |
| Human approval of held sends | A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. | Shipped |
| Drafts | Agents write drafts that a person edits and sends, over the API, MCP, JMAP, IMAP and the webmail. It is the documented path for draft-only inboxes: sending a draft needs the approval permission agents do not hold. | Shipped |
| Scoped API keys | Keys bound to the organization, one pod or one inbox, holding only the scopes they are given. A key cannot mint a key wider than itself. | Shipped |