Read in step 2 of `SKILL.md`. A thread matching a row here is class 2 (Systemmail nach Muster) and goes to the target folder as a batch item, unless the row says otherwise. Several systems share one sender address, so a row matches only when sender **and** subject fit. Folder paths are relative to `Inbox/`.
Source: inventory of the inbox 06.–13.11.2026. The Outlook rules in `/home/sascha.koenig/ap/PM/.okf/systems/outlook.md` cover the same patterns at delivery time; this file catches what arrives before a rule exists or slips past one.
| `bot@az-gruppe.com` | `AKZEPTIERT:`, `Herausgabe wurde akzeptiert`, `Asset herausgegeben`, `Gegenstand akzeptiert` | asset management notice (display name "AZ - Asset Management") | archive | an asset checked out **to Sascha** that he has not accepted yet → `Für dich:` |
| `bot@az-gruppe.com` | `hat die Einladung für Metabase angenommen` | Metabase invitation accepted | archive | |
| `bot@az-gruppe.com` | `Invitation to` … `accepted` | Vaultwarden invitation accepted | stays in `Inbox` | needs Sascha: confirm the user in Vaultwarden → `Für dich:` |
| `noreply@azintec.com` | `Freigabe Rechnung vom` | Sage invoice approval | stays in `Inbox` | class 3 (Freigabe); display names "Sage Rechnungsprüfung" and "Prüfprozess" |
| `account-service@azintec.com` | `Passwort läuft bald ab` | password expiry | stays in `Inbox` | `Für dich:` |
| `MSSecurity-noreply@microsoft.com` | `synchronization errors in your directory` | Entra Connect sync alert | `Alarme` | recurring since August 2026; name once under "Prüfen" with the count |
| `no-reply@d-velop.cloud` | `Nutzerkonto angelegt` | account created | `Inbox` → archive | class 7 |
| `security@info.n8n.io` | `Security Update` | security bulletin | stays in `Inbox` | `Für dich:` (decide whether to patch) |
| `support@mailgun.zendesk.com` | `[Request #` | vendor support ticket | stays in `Inbox` | a person waits for an answer: class 6 |
| any internal person | `Zugesagt:`, `Angenommen:`, `Accepted:` | meeting acceptance | `Kalender` | |
| any internal person | `Abgelehnt:`, `Declined:` | meeting decline | `Kalender` | has body text → read it first; information in it goes into the Lagebild |
| any internal person | `Automatische Antwort:` | out-of-office | `Kalender` | |
## Newsletters and cold outreach
Target `Newsletter`. Match on the sender address, or on the domain where marked.
| `updates@learn.mailgun.com` | onboarding series |
| `kunde@ibes.ag` | supplier newsletter |
| `notifications@email.link.com` | marketing |
| `luis.semprun@moodle.com` | cold outreach |
| `nicolas@teammood.io` | cold outreach |
| `johannes@ondeva.com` | cold outreach |
| `hirs@swisscom-tech.de` | cold outreach |
A mail from a known supplier contact that reads like outreach but refers to running business (an open order, an agreed date) is no newsletter: classify it normally. Two senders seen so far need that check every time: `rysanek@raynet.cz` (Raynet is a running vendor) and `Kundeninformation@information.dsv.com` (DSV customer notices can change invoice handling).
## Shared mailboxes
The sender address is a mailbox, the person is in the signature. The signature decides; the table is only the usual case.
| Mailbox (local part) | Usually |
|---|---|
| `Finanzen@…` | Conny Buchwald |
| `FinanzenAZP@…` | Conny Buchwald |
| `erechnung@…` | Conny Buchwald |
| `auftrag.cz@…` | Kateřina Brudíková |
## Adding a pattern
A system sender that matches no row is handled once as a single proposal. In the same proposal list add one numbered item: the new row for this file (sender, subject fragment, kind, target). After approval write the row here, and name the matching Outlook rule as a `Für dich:` point, since the connector cannot create rules.