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 automation.

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.

Gmail's Sent folder is named [Gmail]/Sent Mail, not Sent, so saving fails after SMTP delivery succeeds. Add folder.aliases entries using the plural dotted-key syntax under your account; the older singular folder.alias form is silently ignored in v1.2.0.

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

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 the message is sent.

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