himalaya-email-rust

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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

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

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

```bash
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](https://github.com/pimalaya/himalaya/blob/v2.0.0/README.md)
- [Himalaya releases](https://github.com/pimalaya/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`

Inspect accounts and connectivity:

```bash
himalaya account list --json
himalaya account check --account "Account Name" --json
```

Run bare `himalaya` for the account discovery wizard.

### IMAP and SMTP

```toml
[accounts.gmail]
default = true

imap.server = "imaps://imap.gmail.com:993"
imap.sasl.plain.username = "user@example.com"
imap.sasl.plain.password.command = ["pass", "show", "gmail"]

smtp.server = "smtps://smtp.gmail.com:465"
smtp.sasl.plain.username = "user@example.com"
smtp.sasl.plain.password.command = ["pass", "show", "gmail"]

mailbox.alias.inbox = "INBOX"
mailbox.alias.sent = "[Gmail]/Sent Mail"
mailbox.alias.drafts = "[Gmail]/Drafts"
mailbox.alias.trash = "[Gmail]/Trash"
```

Himalaya does not automatically load `.env` files. Source one explicitly from the password command:

```toml
imap.sasl.plain.password.command = ["sh", "-c", ". /path/to/.env; printf '%s' \"$GMAIL_APP_PASSWORD\""]
smtp.sasl.plain.password.command = ["sh", "-c", ". /path/to/.env; printf '%s' \"$GMAIL_APP_PASSWORD\""]
```

Keep config and secret files private:

```bash
chmod 600 ~/.config/himalaya/config.toml ~/.config/himalaya/.env
```

For Gmail REST API, use an OAuth 2.0 bearer token from a broker such as `ortie`:

```toml
gmail.auth.token.command = ["ortie", "token", "show", "-a", "gmail"]
```

Select it with `-b gmail` when the account has multiple backends. App passwords work with the IMAP/SMTP configuration, not the Gmail REST backend.

## File Handling

Let the caller choose attachment paths. Do not hardcode a machine-specific source path.

When a temporary `.eml` is needed, use the task's working directory or the workspace `Workbench/` directory. Remove temporary MIME files after successful delivery unless the user asks to retain them.

## Path A: Compose and Send

### Plain Email

```bash
himalaya message compose \
  --from sender@example.com \
  --to recipient@example.com \
  --subject "Subject" \
  --body "Email body" \
  --send
```

From Jansen611/Agent-Skills, MIT.

More from Jansen611/Agent-Skills