https://gitlab.synchro.net/main/sbbs/-/issues/1228#note_10274
Verified on Linux against the !730 / `sbbsecho-security-violation-summary` change (built from the matching GitHub tip `d6790e86c`).
Built `sbbsecho` (Clang 18, RELEASE) and tossed real type-2 packets into a minimal SecureEchomail fixture:
- Areas `TESTGEN` / `TESTDEB` linked only to `1:100/2`
- Packets from `1:200/3` with two `AREA:TESTGEN` messages (duplicate pair) plus `1:200/4` with one `AREA:TESTDEB`
- Mid-run still logs `Security violation - %s not in Area File` for every rejected message
- End-of-run summary is exactly:
```
Security Violation: TESTGEN 1:200/3
Security Violation: TESTDEB 1:200/4
```
- Empty inbound (no violations) prints no `Security Violation:` summary lines
Unique-pair summary, duplicate suppression, quiet empty run, and existing mid-run warnings all look good for #1228 / !730.
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)