MAILRAFT / PRODUCT
Features
MailRaft is a disciplined business-email operating system that keeps every outbound message deliberate, approved and traceable. It combines a shared inbox, business-grounded AI drafts, strict human approvals, scoped third-party integrations and a policy-bound REST and MCP developer surface.
The one-line pitch
Business email that behaves like a controlled system of record: AI drafts replies grounded in your own knowledge; a human approves the exact bytes; the system sends through a provider you authorized; every step is logged.
Controlled betaGeneral sending is disabled. The restricted SES worker and Bounce/Complaint suppression have local acceptance tests; application-originated sandbox feedback and AWS production approval remain outstanding. The workflows below include planned capabilities.
Shared inbox for the whole company
A single mailbox view assigns conversations to owners, keeps threads intact across providers and preserves original Message-IDs for cited replies.
- Role-based access: owners, admins, members, reviewers and read-only auditors.
- Server-side search is tenant-scoped so one team never sees another team mail.
- Internal notes stay off the customer thread; threading survives provider migration.
- Attachment quarantine and scanning are required before enabling attachment delivery; the restricted SES worker sends text only.
Grounded AI drafts, never autonomous sends
Drafts are generated from the tenant own uploaded knowledge sources: product docs, policies, past correspondence, support macros. Every draft lists the exact chunk IDs it used so the owner can inspect the sources before approving.
- Prompt injection in email, attachments and web content is treated as untrusted input and cannot widen scope.
- The AI never approves itself, never escalates its own permissions and never retries unknown outcomes.
- Models run through a scoped adapter: no provider raw-prompt pass-through, no tenant data leaking across model calls.
Exact human approval
Each outbound message carries a server-held approval record bound to the exact sender, recipient, subject, body, attachments and thread. Any edit after approval invalidates the approval and forces a new review.
- Approvals record the authenticated owner and review time. Signed approval links are planned.
- Reviewer-must-differ-from-drafter can be enforced for sensitive flows.
- Approvals are cryptographically bound to the message bytes; replay or substitution is detectable.
Suppression and bounce handling by default
A global suppression table blocks sending to any recipient on it before the provider is ever contacted. Hard bounces and complaints auto-suppress.
- SES feedback passes signature checks, deduplicates SNS message IDs and correlates the SES provider MessageId.
- The worker enforces global and tenant suppression. Owners can suppress a lead contact; a full suppression-management screen is not available.
- Unknown transport outcomes are reconciled on provider ID, never blindly retried, never silently failed over.
Scoped provider integrations
Each adapter runs through a shared policy layer with rate limits, scope enforcement, encrypted at-rest credentials, SSRF-safe outbound requests, bounded response sizes and sanitized call history.
| Provider | Scope | Status |
|---|---|---|
| Amazon SES (outbound) | Transactional, approved identities | Verified identity in eu-north-1; sandbox pending production access |
| Google Workspace (inbound) | Gmail readonly | Implemented; live acceptance remains gated |
| Microsoft 365 (inbound) | Mail.Read planned | Roadmap: parallel lane with Gmail |
| Yahoo Mail | OAuth + IMAP/SMTP fallback | Roadmap: after Gmail/Microsoft pilots |
| Generic IMAP/SMTP | Per-tenant scoped credentials | Roadmap: shared mailbox-adapter contract |
| Slack | Approved channels only | Verified install contract |
| Notion | Approved pages only | Verified read/write adapter |
| Airtable | Approved base and table | Verified read/write adapter |
| Apify | Approved actor and budget | Research-only; never implies marketing consent |
| BRIQ / Africa Talking SMS | Owner-approved recipients only | One deduplicated notification per crucial action |
Developer surface
REST API at api.mailraft.com with scoped bearer keys, exact action schemas and a public health endpoint. MCP gateway so the owner tooling can call the same actions under the same policy layer.
- No action, API key or MCP tool can bypass server-side tenant, scope, membership or revocation checks.
- API keys are high-entropy tokens; the raw value is shown exactly once at creation and never recorded.
- Call history is sanitized; secrets, cookies and provider payloads never appear in audit records.
Status and evidence
The public status page reports current endpoint reachability without claiming an uptime SLA. Each release records sanitized evidence covering scope, timestamp, release SHA, environment, fixtures, external side effects and unverified gaps.
Honest by designNothing is marked complete without live proof. A queued job, an accepted SMTP response or an SMS API 200 is not proof of delivery.
What MailRaft is not
- Not a bulk marketing or cold outreach platform.
- Not a replacement for your current mail provider; it sits on top of SES, Gmail, Microsoft or your own SMTP.
- Not an autonomous agent that decides when to send to your customers. A human always approves the bytes.