email-triagelisted

Triage inbox emails, classify by urgency, and batch action them (delete, move, draft reply, skip). ## Accounts Two accounts are configured in himalaya. Use `-a <name>` to target a specific account: | Name | Email | Default | |------|-------|---------| | harlanzw | harlan@harlanzw.com | yes | | hotmail | harlan103@hotmail.com | no | When no `--account` is specified, triage **both** accounts sequentially (harlanzw first, then hotmail). The hotmail account uses OAuth2 via Thunderbird's public client ID; if the token expires, re-auth with `ortie auth get -a hotmail`. ## Gotchas - **IMAP connection timeouts** -- himalaya connects over IMAP. If commands hang, the connection may have dropped. Retry once before reporting failure. - **Hotmail OAuth2 token expiry** -- the hotmail access token expires after ~1 hour. If you get a keyring/auth error, run `ortie auth get -a hotmail` to re-authenticate, then re-store tokens with the himalaya keyring attributes (service=himalaya-cli, username=hotmail-oauth2-access-token/refresh-token, target=default, application=rust-keyring). - **Envelope IDs are session-volatile** -- IDs change after moves/deletes. Always action emails in a single pass; do not cache IDs across steps. - **Delete = move to Trash** -- `himalaya message delete` moves to Trash unless already in Trash. Safe for triage. - **template send is irreversible** -- never send a reply without explicit user confirmation. Always save drafts first using `himalaya template save -f Draf