feat: end-to-end DKIM check through a real Postfix, docs and example config
- Check that every message the list delivered through Postfix is signed with the list domain and still verifies, and that edits break it - Run dkim keygen, record and the no-overwrite rule inside the read-only container - Document DKIM, SPF and DMARC in the README and show the dkim block in the example config
This commit is contained in:
parent
e7cc9cacfb
commit
849a85ec7d
1 changed files with 119 additions and 1 deletions
34
README.md
34
README.md
|
|
@ -5,6 +5,7 @@ A modern, single-binary mailing list manager: an evolution of Mailman.
|
|||
- Postfix delivers to parsimony over LMTP; parsimony relays through SMTP.
|
||||
- Discussion lists with member-only posting, `List-*` headers, one-click unsubscribe
|
||||
and DMARC-safe `From` rewriting.
|
||||
- DKIM signing of outgoing mail with one key per list domain, so DMARC holds after the From rewrite.
|
||||
- Durable outbound queue: a post is accepted once it is stored, one delivery per recipient,
|
||||
and a background worker sends it with retries (1m, 5m, 15m, 1h, 3h, then every 6h, for up to
|
||||
3 days). Relay outages and restarts lose nothing.
|
||||
|
|
@ -89,6 +90,39 @@ of the messages. Messages that cannot be read are listed and counted, and the ex
|
|||
It works whatever the list's archive policy is (the policy only governs live mail). The admin UI has the same import on
|
||||
the Archive tab. Search is accent-insensitive: `caffe` finds "Caffè".
|
||||
|
||||
## Outgoing mail: DKIM, SPF and DMARC
|
||||
|
||||
Parsimony rewrites `From` to the list address, so a signature of the original author's domain is of no use and
|
||||
receivers that enforce DMARC need a signature of the **list domain**.
|
||||
|
||||
```
|
||||
parsimony dkim keygen lists.example.org --selector mail --out /etc/parsimony/dkim-lists.pem
|
||||
```
|
||||
|
||||
prints the DNS TXT record to publish and the config to add (the private key is written with mode 0600 and the
|
||||
command never overwrites an existing key without `--force`):
|
||||
|
||||
```yaml
|
||||
dkim:
|
||||
- domain: lists.example.org
|
||||
selector: mail
|
||||
key_file: /etc/parsimony/dkim-lists.pem
|
||||
```
|
||||
|
||||
Once the record is in DNS, `parsimony dkim check lists.example.org --key FILE --selector mail` looks it up and compares it
|
||||
with the key. Both commands work offline of the API and need no token.
|
||||
|
||||
- A message is signed with the key of the domain in its From address (exact match, else a parent domain), at send time, so
|
||||
the per-recipient `List-Unsubscribe` headers are covered. Relaxed/relaxed, SHA-256, no body length limit.
|
||||
Signed: From, To, Cc, Subject, Date, Message-ID, In-Reply-To, References, Reply-To, MIME-Version, Content-Type,
|
||||
Content-Transfer-Encoding and the `List-*` headers. A relay may add `Received` or rewrite other headers.
|
||||
- A list on a domain without a key is sent unsigned. A broken key file stops the daemon at startup. If signing fails at
|
||||
send time the error is logged and the message goes out unsigned: not delivering is worse than a missed signature.
|
||||
- RSA (2048 bits recommended; PKCS#1 or PKCS#8 PEM) and Ed25519 keys are supported. Some receivers do not verify Ed25519 yet.
|
||||
- Also publish SPF for the machine that relays your mail (for example `v=spf1 ip4:203.0.113.10 -all` on the list domain)
|
||||
and a DMARC record (start with `_dmarc.lists.example.org TXT "v=DMARC1; p=none; rua=mailto:postmaster@example.org"`,
|
||||
then tighten the policy once the reports look clean).
|
||||
|
||||
## Docker
|
||||
|
||||
The image runs as an unprivileged user (uid 65532) and works with a read-only root filesystem.
|
||||
|
|
|
|||
Loading…
Reference in a new issue