Works with Automation consent

`briskmail draft`

Built

Open a compose window with the fields filled in. Saves nothing and cannot send.

Usage

briskmail draft [--to A] [--cc A] [--bcc A] [--subject S] [--body B | --body-file F]

Every field is optional. The window is yours from there: edit it, save it, send it or close it.

Needs macOS Automation consent and no switch.

--to ADDRESSES: Recipients, comma-separated.
--cc ADDRESSES: Cc recipients, comma-separated.
--bcc ADDRESSES: Bcc recipients, comma-separated.
--subject TEXT: The subject.
--body TEXT: The body, as plain text. Not with --body-file.
--body-file PATH: Read the body from a file, or from stdin with -. Use instead of --body. Not with --body.

--account ID: An account id from accounts.json. Leave it out to use the first account. Accepted before or after the command.
--dev: Send the command to the dev build (com.valleyedgeconsulting.edgemail.dev) instead of Briskmail. Only useful when working on Briskmail itself.

Code	Meaning
0	The compose window is open. Prints ok.
2	Not allowed. macOS refused Automation for the app you ran it from (-1743).
3	Briskmail reported an error, printed on stderr.
64	Bad usage, such as --body and --body-file together.

$ briskmail draft --to dana@example.com --subject "Thursday" --body "Can we move to 3pm?"
ok

$ printf 'Notes from today:\n- ship Friday\n' | briskmail draft --to team@example.com --subject Notes --body-file -
ok

A long or multi-line body is easier through stdin than through quotes.