Skip to content

README.md

Latest commit

 

History

History
53 lines (42 loc) · 2.47 KB

README.md

File metadata and controls

53 lines (42 loc) · 2.47 KB
Raw

mail

The inbox from the terminal, for more than one account.

/mail:login signs in to a provider — Gmail, Yahoo, AOL, iCloud, Fastmail, Zoho, Proton (through its Bridge), GMX, Yandex, mail.com, Posteo, mailbox.org, Migadu, Purelymail, Forward Email, or any IMAP host by name — saying which kind of password it wants and checking both logins before storing anything. /mail:inbox lists, searches and reads over IMAP, and marks, files or deletes. /mail:send replies in the original's thread or sends a new message, over the account's SMTP with Resend as the fallback, or files it as a draft.

Install

moshcode plugin marketplace add profullstack/cli-tools
moshcode plugin install mail@cli-tools

Or install the command directly, without the plugin:

curl -fsSL https://raw.githubusercontent.com/profullstack/cli-tools/master/install.sh | sh
mail accounts pull           # accounts from the cli-tools-mail team vault
cli-tools config pull        # the Resend key, for the fallback

The thing worth knowing

The password is the whole problem. Gmail, Yahoo, AOL, iCloud, Fastmail and Yandex refuse the account password over IMAP on purpose and want a generated app password, and their refusal reads like a typo. mail login <provider> says which kind of password the host wants, and where to make one, before asking for it, then tries IMAP and SMTP and stores nothing on a refusal. Outlook.com and Microsoft 365 take only OAuth2 now, and Tuta and HEY have no IMAP at all; mail login says so rather than failing.

Two accounts, two rule sets. A business address on its own domain can send through Resend when SMTP is down, because the team has verified the domain there. A Gmail address cannot: gmail.com is not anyone's to verify, so that account reads and sends only with an App Password, and mail says so rather than trying Resend and reporting a 403.

A reply threads. mail reply carries In-Reply-To and References, answers the Reply-To when one was set, and quotes the original underneath — so the other side's client files it under the same conversation, which is the difference between a reply and a new message that happens to share a subject.

Nothing here names a person. Accounts live in ~/.config/cli-tools/mail.json (0600) or in the vault as MAIL_<NAME>_EMAIL / _PROVIDER / _PASSWORD; the environment's MAIL_<NAME>_PASSWORD wins over the stored one, and mail accounts shows which source is in effect without ever printing a password.