outlook_mail

Outlook Mail

Purpose

Manage Outlook Mail messages with the outlook-mail companion CLI. The connector supports both personal Microsoft accounts and Microsoft 365 work or school accounts.

Tooling

Use exec to run:

outlook-mail <subcommand> [options]

Core subcommands:

• disconnect
• accounts (identity metadata only; never tokens)
• list [--page-size 10] [--unread] [--page-token 20] [--folder sentitems]
• get "<MESSAGE_ID>"
• search "<query>" [--folder sentitems] [--page-size 10]
• send --to alice@example.com [--to bob@example.com] [--cc charlie@example.com] --subject "Hello" --body "Hi ..." [--attachment /path/to/file.pdf]
• reply "<MESSAGE_ID>" --body "Thanks for the update!" [--reply-all]
• delete "<MESSAGE_ID>" (moves the message to Deleted Items; recoverable, not a permanent delete)
• mark-read "<MESSAGE_ID>"
• mark-unread "<MESSAGE_ID>"

Commands use the default linked mailbox unless --account <account_id> is provided. When the user clearly means a particular mailbox, run outlook-mail accounts, match its display_name, and pass its opaque account_id with --account. If the match is ambiguous, ask instead of guessing. Never silently fall back to the default after an account-selection error. --account applies only to mailbox operations; --status, accounts, and disconnect are connector-wide. To remove one mailbox while keeping the others, direct the user to that account under Connectors in Settings; do not run disconnect.

Once an account is selected, repeat the same --account <account_id> on every follow-up that uses results from that mailbox, including pagination with --page-token, get, reply, delete, mark-read, and mark-unread. Message IDs and page tokens belong to the account that returned them.

For mail-finding or search requests where the mailbox is unclear, run outlook-mail accounts first. When more than one mailbox is linked, search each with its own --account; do not say the message is missing until every mailbox returned no match. If a mailbox cannot be searched, say it could not be checked and follow the reauthorization flow below instead of claiming the message does not exist.

Use --page-size for result count. --top, --limit, and --max-results are compatibility aliases only; do not use them in new commands. Use get "<MESSAGE_ID>" for a single message; read, get --id, and search --query are compatibility forms only.

JSON output contract:

• disconnect: parse ok, action, status, and disconnect_url
• list / search: parse ok, count, next_page_token (when present, pass back as --page-token), total_messages, retrieved_at, and messages[] with id, subject, from, to, date, message_received_at, preview, is_read, and has_attachments
• get: parse ok, retrieved_at, and message with id, subject, from, to, cc, date, message_received_at, body, body_type, is_read, and has_attachments
• send: parse ok and action
• reply: parse ok, action, and message_id
• delete: parse ok, action (trashed), and message_id; the moved message gets a new id, so message_id is not the id you passed in — use the returned one for any follow-up command
• mark-read / mark-unread: parse ok, action, and message_id

Auth

Use outlook-mail --status for connector state and link management. The binary handles its callback target internally.

• If outlook-mail --status returns connect_url, replace <connect_url> with the returned URL and share exactly this Markdown link: [Connect Outlook Mail](<connect_url>); do not paste the raw URL separately.
• When the connected response includes add_account_url, share it as [Add Outlook Mail account](<add_account_url>) when the user wants another mailbox.
• If the user wants to disconnect, run outlook-mail disconnect. When disconnect_url is present, replace <disconnect_url> with the returned URL and share exactly this Markdown link: [Disconnect Outlook Mail](<disconnect_url>); do not paste the raw URL separately. Otherwise say it is already disconnected.
• Keep status and linking inside outlook-mail --status; do not use a shared connector helper CLI.
• Never print tokens, cookies, or connector secrets.

Operating Rules

1. Use search for targeted lookup, list for browsing, and get only when you need the full body of a specific message.
2. Message IDs are opaque Graph values. Reuse the exact id returned by list or search.
3. Before send, confirm recipients, subject, and body in the current thread.
4. Before reply, confirm the reply body and whether the user wants --reply-all. Use --reply-all only when the user explicitly wants everyone included.
5. delete, mark-read, and mark-unread may proceed from a clear user request without an additional confirmation. delete moves the message to the Deleted Items folder, where the user can still recover it; tell the user that, and do not describe it as permanent or unrecoverable.
6. For mailbox-summary requests, exclude likely spam, phishing, or irrelevant bulk promotions by default unless the user explicitly asks for junk or spam, and briefly note that filtering if you used it.
7. If any command reports an auth failure, stop and run outlook-mail --status. If it returns connect_url, share the normal connect link. Otherwise run outlook-mail accounts: check the selected account when the failed command used --account, or every account when it did not. For each relevant row with needs_reauth: true, share the status response's add_account_url as [Reconnect Outlook Mail account](<add_account_url>) and ask the user to sign in with that same Microsoft account. Never rerun a failed --account command without --account.
8. Never surface raw Graph identifiers (message ids, conversation ids) or other internal response fields (change keys, @odata fields, page/skip tokens, raw JSON) in text shown to the user — including in summaries, lists, or per-item annotations. Reuse the ids only internally to chain follow-up commands (rule 2). The sole exceptions are when the user explicitly asks for a raw id or you must show one to troubleshoot a failure.
9. The compatibility date field is Outlook's message-received time. Prefer message_received_at.user_local when presenting it. It is not the time of an event described inside the email; never infer a delivery, payment, trip, meeting, or other event time from it.

• Permission-withheld fields: a list/search result carrying a withheld entry had those fields removed by the user's "Access messages" permission — they are NOT empty. Answer from the remaining fields and mention that the permission hides the rest. Only when the user actually needs a withheld field for one specific message and withheld.reason is requires_approval, read that message with get, which shows the user the approval prompt. Never get during routine browsing just to fill previews.