When the global cap of unconfirmed requests (300 an hour) was reached,
a subscribe request silently got no mail while the visitor saw "Check
your email"; a newsletter launch can pass 300 signups an hour.
- limits.pending_per_hour (default 300, must be a whole number >= 1)
is validated at load and set on the store by the app.
- When the global cap refuses a request the store logs a warning naming
the setting, at most once a minute. The visitor still gets the
neutral page, so nothing about members is revealed. The per-address
cap is unchanged and is not logged.
- parsimony.example.yaml documents the setting.
Behind a reverse proxy every visitor shared the proxy's address, so the
whole site got 10 signups an hour and one person could block everyone.
Over IPv6 each address of a /64 was a fresh key, so the limit did not
bind and the map grew by one entry per address.
- web.trusted_proxies (addresses or CIDR ranges, default empty) is
validated at load and passed to the web handler. X-Forwarded-For is
read only when the TCP peer is a trusted proxy; the client is then the
right-most entry that is not itself a trusted proxy. An empty or
malformed header falls back to the peer. With no trusted proxy the
behaviour is unchanged: the header is ignored.
- IPv6 clients are keyed by their /64, IPv4 clients by address.
- The limiter remembers at most 100000 clients. When full it sweeps
expired entries first and otherwise answers 429 to new clients until
the oldest window ends, instead of growing.
- one line of wiring, a commented example in parsimony.example.yaml
- tests: with a rate of 20/s eight deliveries to a sink take at least 350 ms, without a rate they are not paced
- Read the relay password and CA file at startup; refuse to start on an unusable one
- Pass TLS mode, server name, CA pool, credentials and EHLO name to the SMTP relay
- Default the EHLO name to the host name
- Test an authenticating STARTTLS relay, a wrong password (mail stays queued) and the startup checks
- Document external relays in the README and the example config
- Add lmtp.allow: clients outside the list are dropped before the greeting (TCP only)
- Validate the list at load, naming the bad entry
- Warn at startup when LMTP is reachable beyond the machine and no list is set
- Stop publishing the LMTP port in the README and the example config; add Security notes
- 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
- Document delivery semantics, retries and the queue API in the README and OpenAPI
- Add relay.concurrency to the example config
- Test that a relay problem never counts against a member, that the longest-waiting delivery goes first, and the error and limit details
- Show the plain relay error when there is a single batch
- Add web.listen config (default 127.0.0.1:8081, empty disables)
- Start the public web in app, close it with the rest
- Add end-to-end test: archive stays private, becomes public, hides addresses, one-click unsubscribe works
- Cover mutation survivors: attachments, first text part, multibyte cap, member id 0, page clamp, API limit cap, closing connections
- Update OpenAPI, README and example config
- Add config loader with defaults and strict unknown-field rejection
- Add cmd/parsimony wiring store, router, relay and LMTP server
- Handle SIGINT and SIGTERM for graceful shutdown
- Add Dockerfile and example config