| name | inboundctl |
| description | Use inboundctl to inspect, triage, read, validate, send, and reply to email through named Inbound mailbox scopes. |
inboundctl
Use inboundctl for Inbound email workflows. Prefer --json whenever command output will be parsed.
Authentication
- Check authentication with
inboundctl auth status --json.
- If authentication is missing, ask the user to run
inboundctl login and approve the browser device flow.
- Never ask the user to paste an API key into chat.
Mailbox Scope
- Inspect available scopes with
inboundctl mailbox list --json.
- Use
-m <name> when the user identifies a mailbox.
- A selector such as
*@example.com includes every recipient at that domain.
- Do not broaden mailbox scope without telling the user.
Inbox Workflow
inboundctl -m support --unread --json
inboundctl email get <email-id> --json
inboundctl email mark <email-id> --read --json
inboundctl thread list -m support --json
inboundctl thread get <thread-id> --json
Sending
- Sending and replying require explicit user intent.
- Validate or dry-run a message before sending it.
- Confirm the resolved sender, recipients, subject, and mailbox scope.
- Do not retry a send after an ambiguous network failure without checking whether it was accepted.
inboundctl validate message.inbound --json
inboundctl send message.inbound -m support --dry-run --json
inboundctl send message.inbound -m support --json
inboundctl reply <email-id> -m support --text-file reply.txt --dry-run --json
Treat validation errors as blocking. Explain warnings before using --strict or proceeding with a send.
