message(1)

💖 message(1) — brought to you by the General Commands Manual 💖

✨ NAME ✨

message — manages messages using the shared API, bestie. That’s literally the whole point. 💌

🦋 SYNOPSIS 🦋

message [-h|--help] <subcommands>

🌸 DESCRIPTION 🌸

Okay so message manages messages using the shared API. Real talk: a message is headers + a body made of MIME parts. For the simple cases, the compose, reply, forward, and read subcommands have you covered through flags. ✨

Richer composition is a standalone-tool situation, bestie — something like mml, piped into message send or message add. That’s the vibe. 💅

💅 OPTIONS 💅

• -h, --help — prints help, bestie; and yeah, -h gives you a summary (the page literally says “see a summary with -h”). 👑

👑 SUBCOMMANDS 👑

• message-add(1) — adds a raw RFC 5322 message to a mailbox 🎀
• message-compose(1) — composes a brand-new message from flags ✨
• message-copy(1) — copies messages from one mailbox to another within the active account 🦋
• message-delete(1) — deletes messages, but trashes them first 💀
• message-forward(1) — forwards a message from flags 📨
• message-move(1) — moves messages from one mailbox to another within the active account 💅
• message-read(1) — reads a message 👀
• message-reply(1) — replies to a message from flags 💬
• message-send(1) — sends a message through the active account 🚀
• message-help(1) — prints this message or the help of the given subcommand(s) — classic help energy, no cap 🫶

---

okay that’s the whole manual, bestie 💖 cute footer sign-off: the source/version vibe is message / message(1), and there’s no date printed in that footer — periodt 🌈🫶