himalaya

Pipe a message with headers and body into himalaya template send using a heredoc, for example cat << 'EOF' | himalaya template send with From, To, and Subject headers. This non-interactive method avoids opening an editor and works reliably from scripts or agents.

Create an account in ~/.config/himalaya/config.toml pointing to 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.

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

This happens when folder aliases use the outdated singular [accounts.NAME.folder.alias] syntax, which v1.2.0 silently ignores. Save-to-Sent then fails after SMTP succeeds, and retrying sends duplicates. Use the plural folder.aliases.X dotted keys instead.

Yes, compose the message using MML syntax with <#part filename=/path/to/file.pdf> tags inside the body, then pipe it to himalaya template send. MML compiles the parts into proper MIME, supporting multiple attachments, HTML bodies, and inline images.

Use backend.auth.cmd to call a password command such as pass show email/imap, or backend.auth.keyring for the system keyring. Avoid backend.auth.raw, which stores the plaintext password in the config file and is only suitable for testing.