email

Email Management

Manage emails using Himalaya CLI - a powerful command-line email client supporting IMAP, SMTP, Maildir, and Notmuch backends.

Config format note (Himalaya v2.x). Himalaya v2 reorganized the config from the old backend.* / message.send.backend.* schema into per-protocol tables ([accounts.x.imap], [accounts.x.smtp], [accounts.x.jmap]). A v1 config silently loads with zero backends, so every command fails with No backend matching \auto` is configured. If you see that error, the config is in the wrong format — see [references/providers.md](references/providers.md) for the v2 shape. account list` shows the resolved backends per account; use it to confirm.

Agent Usage (Power User Patterns)

When using this skill as an agent, run commands via execute_command. Prefer these patterns:

1. Install and set up if needed. Run Prerequisites Check before the first Himalaya command. If himalaya is missing, fetch the live README and install it. If no account is configured, walk the user through Account Setup, then continue the original request (check mail, etc.). Do not stop at "go install Himalaya".

2. Always use --json (the global flag) when you need to parse results (subject, from, id):

   himalaya envelope list -m INBOX -s 20 --json | jq '.envelopes[] | {id, subject, from, date}'
   

   Note: in v2 the flag is the global --json, not --output json. envelope list emits {"envelopes":[...]}; account list emits {"accounts":[...]}.

3. Non-interactive send uses message write with flags and --send (no editor):

   himalaya message write --to "[email protected]" --subject "Subject" --body "Body text" --send
   

   Or feed the body via stdin:

   printf 'Body text' | himalaya message write --to "[email protected]" --subject "Subject" --send
   

   --save <MAILBOX> appends a copy (e.g. Sent) alongside --send.