mxr forward
Generated from
mxr forward --help. Edit the clap definitions incrates/daemon/src/cli/and re-runnpm run buildinsite/to regenerate.
Forward a message
mxr forward [OPTIONS] <MESSAGE_ID>Arguments
Section titled “Arguments”| Flag | Description |
|---|---|
<MESSAGE_ID> |
Message ID to forward |
Options
Section titled “Options”| Flag | Description |
|---|---|
--account <ACCOUNT> |
— |
--from <FROM> |
Send from this owned address (the account primary or a registered alias). Defaults to the address the original was delivered to |
--to <TO> |
Forward to recipient(s) |
--body <BODY> |
Inline body |
--body-stdin |
Read body from stdin |
--attach <ATTACH> |
File path to attach (repeatable) |
--signature <SIGNATURE> |
Insert this signature by name instead of the scoped default |
--no-signature |
Do not insert any signature |
--yes |
Skip confirmation |
--draft |
Save as a draft instead of sending. Never transmits; the forward lands in mxr drafts, ready to send with mxr send <draft-id>. Mutually exclusive with --yes, so no added flag can turn a draft into a send |
--dry-run |
Show what would be sent |
--format <FORMAT> |
[possible values: table, json, jsonl, csv, ids] |
-h, --help |
Print help |
Use When
Section titled “Use When”Forward a message with optional context. --yes sends; --draft saves the forward as a draft to send later with mxr send.
Everyday Examples
Section titled “Everyday Examples”mxr forward MESSAGE_ID --to teammate@example.commxr forward MESSAGE_ID --to teammate@example.com --body 'FYI' --draft # saves, never sendsSee also
Section titled “See also”- CLI overview — full command index
- Concepts — query operators, search modes, JSON shapes
- Automation contract — which commands support
--format json,--dry-run, stdin