--- title: Work Outlook Mailbox — Basic Auth Disabled (Himalaya) type: incident status: open created: 2026-10-03 updated: 2026-11-12 verified_on: 2026-11-12 confidence: high tags: [email, himalaya, office365, oauth2, auth, incident] sources: [live-himalaya-debug, live-tcp-probe, cron-session-20260826_180700_a94098] --- # Work Outlook Mailbox — Basic Auth Disabled (Himalaya) **Re-verified 2026-11-12 03:3x AWST (stocktake — page was 18d old, inside the staleness window):** the failure is unchanged and still reproduces exactly, with the **same error class**. `himalaya envelope list -a work -s 1` → `Error: cannot build IMAP client / 1: login not supported` — i.e. the server rejects the basic-auth `LOGIN` command itself rather than the credential, which is consistent with the SMTP/IMAP basic-auth shutdown recorded above rather than a changed password. **No remediation has landed since 2026-10-25:** the account still authenticates by password (there is no OAuth2 token in the himalaya config), so path 1 remains the only viable route and still requires Anthony's sign-in. The capability gap described below is unchanged — no cron job polls this mailbox. **Window:** first detected 2026-08-26; re-verified 2026-10-03, 2026-10-25 and 2026-11-12 (still open) **Status:** Open — blocked pending an OAuth2 path **Impact:** The agent cannot read or send from the `work` mailbox. Every work-email request is unanswerable until this is fixed. **Re-verified 2026-10-25 (stocktake):** the failure is unchanged and still reproduces exactly. `himalaya envelope list -a work -s 1` still returns: ``` Error: 0: cannot build IMAP client 1: login not supported ``` No remediation has landed since 2026-10-03 — the account still authenticates by password against a tenant that advertises only `XOAuth2`. Fix Option 1 (OAuth2) remains the only viable path and still requires Anthony's sign-in. ## Symptoms ``` $ himalaya envelope list -a work -s 1 --debug email::imap: connecting to IMAP server outlook.office365.com:993 email::imap: supported auth mechanisms mechanisms=[XOAuth2] Error: cannot build IMAP client Caused by: login not supported ``` Network is *not* the problem: the TCP/TLS connection to `outlook.office365.com:993` succeeds and the server completes its capability exchange. The failure is purely at the authentication step. ## Root Cause The account is configured for **password** auth, and the tenant no longer accepts it. - Account config (`~/.config/himalaya/config.toml`, account `work`) sets `backend.type = "imap"`, `backend.host = "outlook.office365.com"`, `backend.login = ""`, `backend.auth.type = "password"` with a helper script at `~/.config/himalaya/get_work_outlook_password.sh`. The SMTP half (`smtp.office365.com:587`, start-tls) is configured the same way. - The server advertises **only `XOAuth2`**. Basic authentication for IMAP/SMTP is disabled at the Microsoft 365 tenant level — a WA Government tenant policy, not a wrong password. Retrying the helper script can never succeed. This is the same wall hit on 2026-08-26: the account was set up that day and every attempt to list folders returned a login rejection. The mechanism list has since *narrowed* — on 2026-08-26 the tenant rejected plain password login despite still advertising `AUTH=PLAIN`; by 2026-10-03 only `XOAuth2` is offered. The personal Gmail account is unaffected (Google still allows app passwords), so this is specific to the work tenant. ## Fix Options 1. **OAuth2 for the `work` account — preferred, needs Anthony.** Requires an app registration in the tenant with the IMAP/SMTP delegated scopes, a device-code or interactive sign-in to mint a refresh token, and `backend.auth.type = "oauth2"` plus token storage in the himalaya config. Anthony's normal login is *number-matching approval in Microsoft Authenticator* — that is exactly the device-code / interactive OAuth flow, so the human step is one sign-in. Tenant admin consent may still be required. 2. **Tenant exception** — an admin re-enables IMAP/SMTP basic auth or issues an app password. Unlikely on a government tenant; not worth relying on. 3. **Alternative access path** — browser/OWA session or Microsoft Graph. Slower and more brittle than native IMAP, but needs no admin action. 4. **Do not** keep re-running the password helper. The credential is not the fault. ## Consequences for tooling - The `email/mail-lookup` skill resolves the account by address before searching; when the requested mail lives in the `work` mailbox it will reach this failure and must report the account as unreachable rather than as "no results found". - No cron job currently polls the work mailbox, so this is an on-demand capability gap, not a background failure. ## Related - [[systems/messaging-integrations]] - [[systems/scheduled-tasks]]