wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,8 @@ title: "Gmail Read-State Incident (2026-08-29)"
|
||||
type: incident
|
||||
status: active
|
||||
created: 2026-08-29
|
||||
updated: 2026-08-29
|
||||
verified_on: 2026-08-29
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: high
|
||||
tags: [email, gmail, cron, himalaya, incident]
|
||||
sources: [session:default/20260829_204103_9e1087]
|
||||
@@ -59,6 +59,32 @@ Despite using `--preview`, Himalaya may still mark messages as read depending on
|
||||
- `goimapnotify` stopped
|
||||
- Important-mail monitor paused (if it existed)
|
||||
|
||||
> **Re-verified 2026-10-20 — the mitigation has partially REGRESSED, and the root cause is still
|
||||
> live.**
|
||||
>
|
||||
> | Item | State on 2026-08-29 | State on 2026-10-20 |
|
||||
> |---|---|---|
|
||||
> | `goimapnotify.service` | stopped | **ACTIVE again** — `systemctl --user is-active goimapnotify.service` → `active`, PID 383 `/home/hermes/go/bin/goimapnotify -conf /home/hermes/.config/goimapnotify/goimapnotify.yaml` |
|
||||
> | Important-mail monitor (`d40085da631c`) | paused | **still paused** — `enabled: False` in `jobs.json`, `last_status: ok` |
|
||||
> | `fetch_newsletters.py` line 49 | patched to `--preview` | **still `himalaya message read --preview --folder INBOX`** — the unsafe call is still in the file, unfixed |
|
||||
>
|
||||
> **So the real fix — rewriting `fetch_newsletters.py` to use readonly IMAP (`SELECT readonly` /
|
||||
> `BODY.PEEK[]`) — has still not been done 52 days later.** The two mitigations that were applied
|
||||
> are one of them gone (goimapnotify restarted) and one still holding (the important-mail monitor
|
||||
> remains disabled).
|
||||
>
|
||||
> **Other email crons currently in `error` state (2026-10-20 read of `jobs.json`):**
|
||||
> `85edf6772bca` Tech & AI Newsletter Digest, `08eb86f02d37` Gmail Action Digest,
|
||||
> `06a0a1c8704f` AI Newsletter Curation for Patrick. Their most recent failures were
|
||||
> provider-side (OmniRoute 503 resource pressure on 2026-10-19; a connection error on 2026-10-15),
|
||||
> **not** read-state errors — but the read-state exposure persists regardless, because the
|
||||
> newsletter fetch path still issues `message read`.
|
||||
>
|
||||
> **Recommended action (not taken here — this is a wiki job, and the fix touches Anthony's mail):**
|
||||
> rewrite `fetch_newsletters.py` to use readonly IMAP, and decide whether `goimapnotify` should be
|
||||
> running. See [[systems/scheduled-tasks]] and the Gmail IMAP lessons in
|
||||
> [[runbooks/provider-health]].
|
||||
|
||||
**Fix required:**
|
||||
- Rewrite `fetch_newsletters.py` to use readonly IMAP (`BODY.PEEK[]`) instead of `himalaya message read`
|
||||
- Audit all Gmail-related scripts for similar patterns
|
||||
|
||||
Reference in New Issue
Block a user