update notification

Author: sspaeti

docs/content/docs/notifications.md

@@ -7,6 +7,9 @@ neomd can fire desktop notifications via `notify-send` (or any compatible CLI) w
 
 Notifications fire from the **TUI only**. The headless daemon (`neomd --headless`) screens mail silently so notifications don't end up on a NAS where no one sees them.
 
+How it looks:
+![notification](/images/notifictation.png)
+
 ## Quick start
 
 1. Make sure `notify-send` is installed and a notification daemon is running (`mako`, `dunst`, `swaync`, …). On Hyprland with mako:

docs/content/docs/screener.md

@@ -32,6 +32,7 @@ spammy@ssp.sh           # … except this one address, which is blocked
 
 Domain entries work in every screener list (`screened_in`, `screened_out`, `feed`, `papertrail`, `spam`, `notify`). The `Di` / `Do` chord (see below) writes them for you from inside neomd.
 
+
 ## Auto-screen and background sync
 
 By default neomd screens your inbox automatically so you never have to press `S`:
@@ -96,6 +97,29 @@ Emails are only auto-screened while they are in the **Inbox**. Once moved to ToS
 
 If emails end up in ToScreen incorrectly (e.g. screened by another device like [Termux with Android](configuration/android) with incomplete lists), use `:reset-toscreen` to move them back to Inbox where auto-screen will re-classify them.
 
+## Priority Screener: Exact match over `@domain` match
+
+When an incoming sender could match more than one list, neomd picks a category in two passes:
+
+1. **First pass — exact email** is looked up in every list, in this priority order:
+   `spam` → `screened_out` → `feed` → `papertrail` → `screened_in`.
+   The first list that contains the *exact* address decides the category, and the search stops.
+2. **Second pass — `@domain` rules** are consulted only if the first pass found no exact match, again in the same priority order. The first list whose `@domain` entry matches decides the category.
+3. If neither pass matches → the sender lands in `ToScreen`.
+
+This guarantees that a per-address rule **always overrides** the broader domain rule across *any* category. Two real examples:
+
+| `screened_in.txt` | `screened_out.txt` | Sender                | Result      | Why                                                                             |
+| ----------------- | ------------------ | --------------------- | ----------- | ------------------------------------------------------------------------------- |
+| `neomd.demo@ssp.sh` | `@ssp.sh`        | `neomd.demo@ssp.sh`   | **Inbox**   | Exact match in `screened_in` (pass 1) wins over `@ssp.sh` block (pass 2)        |
+| (empty)           | `@ssp.sh`          | `neomd.demo@ssp.sh`   | ScreenedOut | No exact match anywhere → `@ssp.sh` in `screened_out` matches in pass 2         |
+| `@ssp.sh`         | `spammy@ssp.sh`    | `spammy@ssp.sh`       | ScreenedOut | Exact match in `screened_out` (pass 1) wins over `@ssp.sh` approval (pass 2)    |
+| `@ssp.sh`         | (empty)            | `random@ssp.sh`       | **Inbox**   | No exact match → `@ssp.sh` in `screened_in` matches in pass 2                   |
+
+**The mental model:** *"Add the domain to lift the whole company, then surgically block (or approve) individual addresses without restating the rule."*
+
+The same two-pass logic runs for [`notify.txt`](/docs/notifications/#domain-entries) too — an exact entry there always wins over an `@domain` entry, but for the notify list this rarely matters since both produce the same outcome (a desktop notification).
+
 ## Colon commands
 
 Press `:` to open the command line. Tab cycles through completions; Enter runs the command.