himalaya-email-rust

Himalaya Email Manager

Manage email with Himalaya v2.0.0+. Primary: built-in v2 commands. For simple email attachments, use message compose --attach. For rich MIME, signing, encryption, or custom formatting, generate a valid .eml file and pass it to message send.

All commands are stateless. Check the installed binary's --help when a command or flag is version-sensitive.

Decision

1. Check the binary and account first: himalaya --version and himalaya account check --json.
2. For a normal text email or ordinary attachment, use Path A (message compose).
3. For multipart MIME or custom headers, use Path B (message send with .eml).
4. For Gmail SMTP, do not pass --save sent unless a duplicate Sent copy is explicitly requested. Gmail normally saves sent messages automatically.
5. For machine processing, use --json and keep the mailbox together with every message id.

Environment Check

command -v himalaya
himalaya --version
himalaya account list --json
himalaya account check --json

If Himalaya is not in PATH, check the common Cargo location:

test -x "$HOME/.cargo/bin/himalaya" && "$HOME/.cargo/bin/himalaya" --version

Install a stable release using the official release assets or installer. OAuth and secret storage are provided through external tools such as password managers and token brokers.

Official references:

• Himalaya README
• Himalaya releases

Safety

• Never print, log, or include passwords, app passwords, OAuth tokens, or .env contents.
• Verify the recipient, subject, body, and attachment paths before sending.
• Do not use --save sent for Gmail SMTP unless a manual Sent copy is required.
• Use --log-level off when clean JSON output is required.

Configuration

Config files are loaded from the first valid path among:

• $XDG_CONFIG_HOME/himalaya/config.toml
• $HOME/.config/himalaya/config.toml
• $HOME/.himalayarc