# Send mail from the person's own address

> Send mail from the person's own address: 2 companies fully do it, 8 with a limit, 24 carry the tag. Every listing in Mailbox access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/mailbox-access.send-as-user/
- Markdown: https://www.anchorterminal.com/niches/mailbox-access.send-as-user/index.md (~1,300 tokens)
- Slim: https://www.anchorterminal.com/niches/mailbox-access.send-as-user/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/mailbox-access.send-as-user/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 24 | 14 | 5 |

## What counts as done

One copy of the message is delivered with the full body intact and appears in the Sent folder, confirmed by message ID; a retry after a timeout sends nothing twice.

How agents ask for it: send this reply; email the client the summary; send the follow-up from my account

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **EmailEngine (Postal Systems OÜ, Narva mnt 5, 10117 Tallinn, Estonia, registry code 14971894)**: Submit takes an Idempotency-Key and echoes it, the 2xx means queued and the outcome follows through messageSent or messageFailed webhooks, and sent mail lands in Sent (uploaded for SMTP, filed by Gmail and Graph).
- **Nylas Email API (Nylas, Inc.)**: POST /messages/send takes an Idempotency-Key header, up to 256 characters, so a retry doesn't send twice, and returns the sent message with its ID, with headers on request.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Aurinko Email API (Yoxel, Inc.)**: POST /v1/email/messages and drafts/{id}/send send mail, but the spec has no idempotency key, so a retry after a timeout can deliver twice unless the agent first searches rfc822msgid:.
- **email-agent-mcp (UseJunior)**: A duplicate-delivery guard refuses an identical send repeated within 15 minutes and sends are allowlist-gated, but Graph and Gmail sends below take no idempotency key, and the README doesn't say a message ID confirms delivery.
- **Fastmail API (JMAP) (Fastmail Pty Ltd, ACN 142 646 580, PO Box 234, Collins Street West, VIC 8007, Australia)**: EmailSubmission/set sends a stored Email and onSuccessUpdateEmail can move it to Sent, but there is no idempotency key, and the listing notes say the customer terms forbid programmatically generated mail to outside addresses.
- **Gmail API (Google LLC)**: messages.send posts a raw RFC 2822 message and returns its ID in Sent, but there is no idempotency key, so a retry after a timeout can send twice.
- **Himalaya (No legal entity found. Copyright Clément DOUIN (soywod))**: message send and compose --send transmit over SMTP or the provider API, but no idempotency key or returned message ID is documented, and acc-21 found invalid UTF-8 truncating a message that was sent with a success message (fixed 12 October).
- **Outlook Mail (Microsoft Graph) (Microsoft Corporation)**: sendMail saves to Sent Items but answers 202 Accepted with no body or message ID, which the docs say doesn't mean processing finished, and takes no idempotency key; creating a draft then calling send gives an ID to check.
- **Unipile (UNIPILE SAS)**: Send takes an Idempotency-Key and returns tracking_id and provider_id, but keys are held in memory for up to 24 hours and cleared by an application restart or maintenance, so a retry across one can send twice.
- **Zoho Mail API (Zoho Corporation Private Limited)**: POST /api/accounts/{accountId}/messages sends mail, but no idempotency key appears in the index, the listing notes cap external sending at 50 to 500 an hour, and the usage policy lists automated email among uses not allowed.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **CloudPost (CloudPost (James Brooks))**: No docs; the site says the person checks the sending account, recipients and message before approving, but no idempotency, message ID or Sent-folder behaviour is described.

## What stops agents finishing

- no idempotency key on send (Gmail, Graph, Aurinko, Fastmail)
- a 2xx that means queued, not sent
- provider terms against machine-generated mail to outside addresses (Fastmail, Zoho)
- trial or reputation send caps reached mid-task

## Around it

Before: mailbox-access.draft-reply. After: crm.log-activity.

## Where this comes from

Weight 14 of 100 in Mailbox access: 5 of 36 counted mentions (acc-07, 15, 21, 31, 35)

As data: https://www.anchorterminal.com/api/v1/use-cases/mailbox-access.send-as-user.json, or the MCP tool get_use_case with id mailbox-access.send-as-user. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
