78 lines
6.0 KiB
Markdown
78 lines
6.0 KiB
Markdown
# Known mail patterns
|
||
|
||
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.
|
||
|
||
## System mails
|
||
|
||
| Sender | Subject contains | Kind | Target | Note |
|
||
|---|---|---|---|---|
|
||
| `bot@az-gruppe.com` | `[Ticket#` | Zammad notification | `Helpdesk` | do not read these for questions to Sascha; step 1 gets mentions from the API |
|
||
| `bot@az-gruppe.com` | `Helpdesk-Anmeldung von einem neuen Gerät` | Zammad login notice | `Alarme` | under "Prüfen" |
|
||
| `bot@az-gruppe.com` | `Vaultwarden Login Verification Code` | one-time code | `Codes` | |
|
||
| `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 |
|
||
| `Office365Alerts@microsoft.com` | `alert:` | M365 alert | `Alarme` | under "Prüfen", always |
|
||
| `quarantine@messaging.microsoft.com` | `messages in quarantine` | quarantine digest | `Alarme` | under "Prüfen" |
|
||
| `budgets@costalerts.amazonaws.com` | `AWS Budgets` | budget alert | `Alarme` | under "Prüfen" |
|
||
| `no-reply@raynet.cz` | `Successful login from new location` | login notice | `Alarme` | under "Prüfen" |
|
||
| `no-reply@sharepointonline.com` | `wants to access` | SharePoint access request | stays in `Inbox` | `Für dich:` |
|
||
| `no-reply@sharepointonline.com` | `Besprechungsaufzeichnung ist abgelaufen` | recording expired | `Alarme` | |
|
||
| `noreply@workist.com` | `Dein Workist Fortschrittsbericht` | progress report | `Newsletter` | until unsubscribed |
|
||
| `notifications@app.basecamp.com` | `Basecamp (Community)` | community digest | `Newsletter` | until unsubscribed |
|
||
| `notifications@app.basecamp.com` | `added you to a project` | project invitation | `Inbox` → archive | class 7 |
|
||
| `no.reply@upsbilling.ups.com` | `Neue Rechnungen sind jetzt verfügbar` | UPS invoice notice | `Belege` | |
|
||
| `notifications@frappecloud.com` | `Invoice` | invoice | `Belege` | |
|
||
| `notifications@frappecloud.com` | `Insufficient balance` | payment problem | stays in `Inbox` | `Für dich:` |
|
||
| `notifications@frappecloud.com` | `OTP for Frappe Cloud Login` | one-time code | `Codes` | |
|
||
| `invoice+statements@sally.io` | `Zahlungsbeleg` | receipt | `Belege` | |
|
||
| `invoice+statements+…@stripe.com` | `receipt from` | receipt | `Belege` | sender address varies after `+` |
|
||
| `support@mailgun.net` | `login passcode` | one-time code | `Codes` | |
|
||
| `no-reply@account.canva.com` | `login code` | one-time code | `Codes` | |
|
||
| `no-reply-…@mail.anthropic.com` | `sicherer Link zu Claude` | login link | `Codes` | sender address varies |
|
||
| `customercare@gotowebinar.com` | `Webinar` | webinar reminder / thanks | `Newsletter` | |
|
||
| `do-not-reply@eecpro.knowbe4.com`, `donotreply@knowbe4.com` | `KnowBe4` | report / order confirmation | `Belege` | |
|
||
| `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.
|
||
|
||
| Sender | Kind |
|
||
|---|---|
|
||
| `updates@e.nextcloud.com` | newsletter |
|
||
| `news@llamaindex.ai`, `marketing@llamaindex.ai` | newsletter |
|
||
| `no-reply@cncf.io` | newsletter |
|
||
| `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.
|