himalaya

Pipe a message with headers and body into himalaya template send using a heredoc, for example cat << 'EOF' with From, To, and Subject headers. This non-interactive approach avoids opening an editor and works reliably in scripts and agent workflows.

Set the IMAP host to imap.gmail.com port 993 and SMTP to smtp.gmail.com port 587 with an app password. You must also map folder aliases like sent to [Gmail]/Sent Mail, otherwise saving sent messages fails after delivery.

Duplicates happen when folder aliases use the old singular alias syntax, which v1.2.0 silently ignores. Save-to-Sent then fails after SMTP delivery succeeds, and any retry re-runs the send. Use the plural folder.aliases.X dotted keys instead.

Yes, define multiple [accounts.NAME] sections in config.toml and mark one as default. Switch between accounts at runtime with the --account flag, for example himalaya --account work envelope list.

Yes, use backend.auth.cmd to call a password manager like pass, or backend.auth.keyring for the system keyring. Raw passwords via backend.auth.raw are supported but recommended only for testing.

Use MML syntax in the message body with a part tag specifying the filename, such as <#part filename=/path/to/file.pdf><#/part>. Himalaya compiles MML parts into proper MIME attachments when sending.