mbox(1)

πŸ“¦ version 2.2.1, in arch rolling, nixpkgs unstable

πŸ’– mbox πŸ’–

ok so bestie, you've found yourself in the <pink>General Commands Manual</pink> and this is the page for mbox(1) β€” the mbox-specific API. come sit with me, this one's short and sweet and honestly kinda iconic πŸŽ€

✨ NAME ✨

mbox β€” the mbox-specific API. that's it, that's the whole vibe. no cap.

🌸 SYNOPSIS 🌸

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

πŸ¦‹ DESCRIPTION πŸ¦‹

mbox-specific API. literally what it says πŸ’…

okay so here's the tea: this command gives you access to the raw mbox API. and what does that mean? it means

  • one file per mailbox
  • flags stored in the Status, X-Status and X-Keywords headers

that's the whole model, bestie. one file = one mailbox. flags live in the headers. periodt. 🫢

🌈 OPTIONS 🌈

  • -h, --help β€” print help. and note that if you tack on -h all by itself, you get the summary version instead πŸ’–

πŸ‘‘ SUBCOMMANDS πŸ‘‘

okay this is where it gets good β€” mbox has a whole little family of subcommands, each with their own manpage. let me introduce you πŸŽ€

  • mbox-create(1) β€” create an mbox ✨
  • mbox-rename(1) β€” rename an mbox πŸ¦‹
  • mbox-delete(1) β€” delete an mbox πŸ’€
  • mbox-list(1) β€” list mbox files πŸ“
  • mbox-message(1) β€” manage mbox messages πŸ’Œ
  • mbox-flag(1) β€” manage mbox flags 🚩
  • mbox-help(1) β€” print this message, or the help of the given subcommand(s) 🫢

ngl bestie, maybe read a couple of those subcommand pages before you go wild β€” they're right there and they do all the actual work πŸ’…

okay that's the page!! this little cutie came to you from <purple>mbox(1)</purple>, filed under the <pink>General Commands Manual</pink> β€” same mbox name up top, same mbox name at the bottom, no date on this one but she's timeless anyway. go be the main character of your mailbox πŸ§šπŸ’œ

πŸ“¦ where this page comes from