himalaya

Pipe a message with headers and body via stdin to himalaya template send, for example using a heredoc with From, To, and Subject headers. This non-interactive approach avoids opening an editor and is the recommended method for scripted or agent-driven sending.

Create a config.toml account with imap.gmail.com:993 and smtp.gmail.com:587, using an app password if 2FA is enabled. You must also set folder.aliases mapping sent to [Gmail]/Sent Mail, drafts to [Gmail]/Drafts, and trash to [Gmail]/Trash.

This happens when folder aliases use the outdated singular folder.alias syntax, which v1.2.0 silently ignores. Save-to-Sent then fails after SMTP delivery succeeds, and retrying the non-zero exit re-runs the send. Use the plural folder.aliases.X dotted keys instead.

Yes. Download attachments with himalaya attachment download followed by the message ID, optionally specifying a downloads directory. To attach files when sending, use MML syntax with part tags referencing the file path inside the composed message.

Yes. Define multiple account sections in config.toml and mark one as default. List accounts with himalaya account list and select a specific one at runtime using the --account flag before any command.

Avoid raw passwords in config.toml. Instead use backend.auth.cmd to call a password manager such as pass, or use backend.auth.keyring with the system keyring. OAuth2 token-based authentication is also supported for providers that offer it.