Skip to content

mxr forward

Generated from mxr forward --help. After editing crates/daemon/src/cli/, update and review the snapshots with scripts/cargo-test -p mxr --test integration cli_help::, then rebuild site/.

Forward a message

mxr forward [OPTIONS] <MESSAGE_ID>
Flag Description
<MESSAGE_ID> Message ID to forward
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> --expected-revision <reviewed-revision> --expected-workspace '<owner-json>'. 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

Forward a message with optional context. --yes prints the operation ID and recovery query to stderr before sending; query it after an uncertain response instead of rerunning, which creates a new draft. --draft saves the forward as a draft. For a saved draft, preview it with mxr send DRAFT_ID --dry-run --format json, then send with --expected-revision REVISION_FROM_PREVIEW, --operation-id OPERATION_ID_FROM_PREVIEW and --expected-workspace '<OWNER_JSON_FROM_PREVIEW>'. Use that same quoted owner for mxr send-outcome and for scheduling with --at TIME.

Terminal window
mxr forward MESSAGE_ID --to teammate@example.com
mxr forward MESSAGE_ID --to teammate@example.com --body 'FYI' --draft # saves, never sends