wiki audit 2026-10-03: cliprox second job confirmed (2/3), work-mailbox incident page, streak recount, skills-index 341->344

This commit is contained in:
Tony0410
2026-10-03 00:18:51 +08:00
parent 0c4ed3350b
commit b9f69d3f75
10 changed files with 296 additions and 51 deletions
+8 -4
View File
@@ -3,11 +3,11 @@ title: Messaging Integrations
type: system
status: active
created: 2026-07-22
updated: 2026-10-02
verified_on: 2026-10-02
updated: 2026-10-03
verified_on: 2026-10-03
confidence: high
tags: [messaging, telegram, discord, email, integrations]
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json, live-himalaya-debug]
---
# Messaging Integrations
@@ -34,9 +34,13 @@ sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
- **Platform toolsets:** cli, discord
## Email
- **Status:** connected
- **Libraries:** himalaya CLI available
- **Platform toolsets:** cli
- **Status: ⚠ partially broken — the personal account works, the `work` account does not.**
- **Personal (Gmail):** connected and usable. Google still permits app-password auth.
- **`work` (Outlook / Microsoft 365):** **unreachable.** `himalaya envelope list -a work` fails with `Error: cannot build IMAP client / Caused by: login not supported`. The account is configured for password auth (`backend.auth.type = "password"` + `~/.config/himalaya/get_work_outlook_password.sh`) while the tenant advertises **only `XOAuth2`** — basic auth for IMAP/SMTP is disabled tenant-wide. The TCP/TLS connection to `outlook.office365.com:993` succeeds; only the login is refused. This is a policy wall, **not a wrong password** — re-running the credential helper cannot fix it. See [[incidents/2026-08-26-work-outlook-basic-auth-disabled]].
- Fix path: OAuth2 (`backend.auth.type = "oauth2"` + token store) after an app registration with IMAP/SMTP scopes; Anthony's normal Office sign-in is number-matching approval in Microsoft Authenticator, which is the device-code flow this needs. Tenant admin consent may be required.
- Consequence for tooling: `email/mail-lookup` resolves the account before searching, so a request for work mail will reach this wall and must report the account as unreachable — not as "no results found".
## Slack
- **Status:** available (toolsets: cli, slack-platform)