fix(security): hold posts whose From header does not match the sender

- Judge membership on the envelope sender and require the From header to name the same address
- Hold mismatches (and missing, unparsable or multiple From addresses) for the admin instead of delivering
- Record why a message was held: new held.reason column, migrated, shown in the API, CLI and UI
- Accept an empty message in the held queue
- Document who may post
This commit is contained in:
tgiachi 2026-11-09 20:23:07 +01:00
commit eb9e915805

View file

@ -208,6 +208,11 @@ lists.example.org lmtp:inet:127.0.0.1:2424
The daemon logs a warning at startup when LMTP is reachable beyond the machine and `lmtp.allow` is empty.
`allow` does not apply to unix sockets: use the permissions of the socket file.
- **Who is posting.** A post is accepted when the SMTP sender is a member *and* the `From` header names the same
address. The SMTP sender can be forged by anyone who can send mail to your MX, and the archive, the rewritten `From`
and `Reply-To` come from the header; so a post whose header names someone else (or has no usable `From`, or several
addresses) is held for moderation instead of delivered, with the reason shown to the admin (API, CLI, UI). Let Postfix
reject forged senders too (SPF, DKIM, DMARC checks on inbound mail).
- The API and the admin UI use one bearer token and no TLS: put them behind a reverse proxy with TLS and keep the `api`
listener private.