- posts ls <list> [--limit N] prints ID, DATE, SUBJECT, RECIPIENTS, SENT,
PENDING, FAILED and DROPPED, newest first, "No posts yet." when empty,
and the API's JSON with --json
- cells go through the same control-character escaping as the other
tables; tests for the table, the limit, JSON, errors and escaping
- GET /api/v1/lists/{id}/posts?limit= returns id, message_id, subject,
created_at, recipients, sent, failed, dropped and pending, newest
first; 404 for an unknown list, 400 for a bad limit, token required
- discarding a queued delivery counts it as dropped (store.DropOutbox)
- openapi: the new path and the discard note
- Deliver and Release (through outbound) queue the deliveries of a list
whose post policy is publishers with priority 1, everything else 0;
confirmation mail stays 0
- tests for Deliver, Release, confirmation mail and the recorded post
- a delivery the relay accepted completes as sent, one given up as
failed, one to a missing mailbox (or with a missing body) is dropped
through store.DropOutbox; a retry changes nothing
- tests: each outcome of a post, giving up after MaxAge, a missing body,
and discussion mail sent before a bigger newsletter queued earlier
- posts table: one row per post queued to a list (message id, subject,
time, recipients, sent, failed, dropped), deleted with the list and
forgotten after 400 days when a new post is recorded
- EnqueuePost and EnqueueFromHeld record the post in the same
transaction and stamp every delivery with its id; a refused duplicate
records nothing; other mail keeps post_id 0
- CompleteOutbox counts sent, the new DropOutbox counts dropped and
FailOutbox counts failed, each in the transaction that changes the
delivery; a delivery that already failed is never counted twice
- outbox priority column; DueOutbox orders by priority, next_at, id
- ListPosts newest first (default 50, at most 200) with Pending derived
- additive migration of the outbox columns, tested on an old database
- Add five screenshots taken from a demo instance: lists, moderation, archive, queue and a public thread
- Cropped to their content and optimised (about 740 kB in total)
- Show the wordmark on the login page and the mark in the header; set the page title to Parsimony
- Put the logo at the top of the README, with a dark-mode variant
- Add PNG exports (a 512 px mark for avatars, a 1200 px wordmark), both transparent
- Say that the logo is under the same licence
- Show the mark on every page, linking to the index, inline so the CSP needs no image source
- Add the favicon as a data: URI and allow img-src data: only
- Add the mark (an envelope in a rounded square) and the wordmark, drawn with monoline strokes so no font is needed
- Add light and dark versions, and the generator script
- Embed them in a Go package and ship the same files with the admin UI
- Test that the SVGs are well formed, need nothing from outside, stay in sync with the admin copies and have enough contrast
- the transport could dial a connection and never use it; the HTTP
server's graceful shutdown waits 5 s for such a connection, which made
the Close tests flaky under -race
- the call and fetch helpers now open one connection per request
- The hint said mail is held only on moderated lists; it is also held when the From
header does not match the sender. It now says both, and shows for every posting policy.
- Test covers members and moderated lists and the hint staying away when messages are held.
- replace the sentence on at-least-once delivery with what is guarded
now (a post queued once per list per hour, approvals always delivered)
- describe the 30 s graceful stop of LMTP and HTTP
- state what remains: at-least-once across the relay, and copies that
arrive after an hour
- router: an approved post is remembered, so the MTA's copy is refused
- store: a post with no recipients stores no message body
- app: an API request in flight during Close gets its answer
- app: finished LMTP sessions leave the connection tracker
- router: drop a TrimSpace on the Message-ID that net/mail already does
- printable() shows C0, DEL and C1 control characters (except tab and newline; CRLF counts
as a newline) as \xNN / \uNNNN, applied to every table cell, archive show, member
listings, import reports and error text, so an escape sequence in a subject cannot
drive the terminal.
- The client refuses to send the bearer token over http:// to a non-loopback host unless
--insecure is given: usage error, exit 2. localhost, 127.0.0.0/8 and ::1 stay allowed.
Offline commands (dkim) never build the client, so they are not affected.
- Tests: the helper, ESC sequences in archive ls/show, held ls, queue ls, list/member names,
API errors and import reports; the URL check by flag and PARSIMONY_URL. README updated.
- api: empty names, '{' in a name, 253/254-character domains, title trimming and the name fallback
- config: an empty query or fragment in base_url
- router: leaving works on a list closed to new members
- store: an expired token is removed when presented
Close cut the LMTP connections while their handlers still ran, so a post
committed to the queue could lose its 250 and be sent again by the MTA.
- Close stops accepting, waits for the LMTP Serve loop to return, then
calls smtp.Server.Shutdown and http.Server.Shutdown with one shared
deadline (shutdownTimeout, 30 s)
- when the deadline passes, the LMTP connections still open are cut
through a tracking listener (smtp.Server.Close is a no-op once Shutdown
began) and the HTTP servers are closed
- the queue worker and the store stop only after that
- tests: a post in flight during Close is queued and gets its 250; a hung
client is cut after the grace period; the open-connections test uses a
short grace period
- openapi: name, domain and title constraints of POST /lists, title of PATCH
- README: the rules, the RFC 2047 List-Id, single-use and re-usable confirmation, rejoin after bounces
- the API + admin UI server and the public web server get ReadTimeout 30s,
WriteTimeout 60s and IdleTimeout 120s next to ReadHeaderTimeout
- the archive import extends its own read and write deadlines to 30
minutes with http.ResponseController, so a big mbox is not cut
- tests: a stalled body and an idle connection are cut on both servers,
an import longer than the default timeouts succeeds, fields are pinned
- README: document the limits and timeouts
name(<=30) + "+confirm-" + 20 = 59 characters, inside the 64 of a local part
(a 30-character name with the old 32-digit token made 71).
- store: CreatePending makes an 80-bit token
- tests: a 30-character list name keeps the confirm and the VERP bounce address (12-digit id) within 64,
and the shorter token still confirms
- discardReason drops only the own-List-Id loop, Auto-Submitted: auto-replied and Precedence: auto_reply; auto-generated, auto-notified and unknown values take the normal path (membership, From, moderation)
- join, leave and confirm commands ignore (250, token kept) a null sender, any Auto-Submitted other than no, Precedence auto_reply/bulk/junk and the list's own List-Id
- tests: loop_test, new auto_test, ingest LMTP test
- README: loops and robots paragraph in the security notes
- store: ConfirmPending claims the row (DELETE ... RETURNING), applies join or leave and commits in one
transaction; a refusal from check, a database error, a token of another list or a rollback leaves the
token usable; concurrent confirmations of one token apply exactly once
- store: CreatePending purges pending rows older than the 72 h TTL
- store: IsActiveMember
- router: confirm uses it, the list policy check runs before anything is consumed
- router: +join from a member disabled by bounces sends the confirmation; confirming re-enables it
- tests: purge, refusal, forced database error, other list, expiry, 8 concurrent confirms, whole rejoin flow
- cli test: the create error text changed with the new name rule
- readLine now holds at most max(limit+1, 1024) bytes of a line and reports its full
length; the rest is read and thrown away, so a single 25 MiB line is no longer read whole.
- The message size is counted from the reported line lengths (after restoring >From),
so the limit is unchanged for normal input.
- Tests: a line over the limit mid-file, at the end of the input and before the first
separator, long lines under the limit, a tiny limit, exact boundary, readLine itself.
- store: migrateMembersV1 renames, creates, copies and drops inside a transaction
- test: a copy that fails on an orphan row leaves the old members table with its rows and no members_v1
- Add the four list-management headers to the list that is already stripped on the way in.
- Drop the author's DKIM-Signature (broken by our header and From changes) and any
Authentication-Results / ARC-* header from outside.
- Tests: every dropped header, repeated ARC headers, and similarly named headers kept.
- message/global-delivery-status (RFC 6533) counts like delivery-status.
- Only the first delivery-status part is read.
- A malformed delivery-status part does not count.
- Drop the redundant empty-boundary check: the multipart reader already
fails on it.
- map router.ErrDuplicate to 250, like a discarded post: the post was
already queued, so the MTA must stop retrying
- test that a post delivered twice over LMTP is queued once
When the reply to a delivered post is lost, the MTA sends the post again
and every member got it twice. The list now remembers the posts it queued.
- store: new delivered table (list id, post id, time), created with
CREATE TABLE IF NOT EXISTS and dropped with its list
- store: EnqueuePost records the post and queues it in one transaction,
returns ErrDuplicate when the list queued it in the last hour, and
purges older records
- store: EnqueueFromHeld records the post too, without refusing it: an
approval always delivers
- router: Deliver uses EnqueuePost and logs a duplicate; the post id is
the Message-ID, or a SHA-256 of the message when it has none
- router: Release passes the post id to EnqueueFromHeld
- tests for duplicates, other ids and lists, expiry on the store clock,
atomicity, posts without Message-ID and approvals
- config: empty is fine; otherwise https with a host, http only for localhost/127.0.0.1/::1, no
userinfo, query, fragment or whitespace; the error names base_url
- test: accepted and refused URLs
- docs: README states the rule
- RunOnce purged failed deliveries (a full scan) on every batch of 50: the Worker now
does it at most once every 5 minutes, by the store clock; a failed purge is retried
on the next run.
- Every recipient re-read the whole message from SQLite: a per-run map msgID -> body,
filled once per message even under concurrency, is dropped when the run ends.
- Tests count purges across batches and after the interval, and body reads per message
(including a missing body) through unexported hooks.
- README: only RFC 3464 reports with Action: failed and a
recipient-unknown code count; bounces count for 30 days.
- openapi: Member.disabled and bounce_count say the count is recent.
- walk at most 10 nested multipart levels and 100 parts, then use what
was found: the post is still delivered, the archive stores less
- read a text part only while it can still become the body, and stop at
the first non-blank plain part, so memory stays near MaxBody
- a Date more than 24 hours after the time of parsing becomes that time;
a Date before 1990 is treated as missing
- tests: 20000-level nesting finishes fast, exact limits, allocation
bound, pathological HTML, date clamps
- headers: the title in List-Id goes through mime.QEncoding, the <id> part stays ASCII
- test: UTF-8 and 200-character titles read back through net/mail and the word decoder
- Add members.bounce_at (unix time of the last counted bounce) with an
additive migration; existing counts get 0, so they are treated as old.
- RecordHardBounce restarts the count at 1 when the last bounce is older
than BounceWindow (30 days); a disabled member stays disabled.
- Tests for the window boundary, the restart and the migration of an
old database.
createList accepted a title with CR/LF (every later post to the list then
failed to rewrite and got 451) and names with '/', '<', '>' or tabs.
- name: lowercased, 1 to 30 characters of a-z 0-9 . _ -, no leading or trailing dot, no ".."
- domain: lowercased ASCII host name, labels of 1 to 63 characters
- title: non-empty single line, at most 200 characters, no control characters
- updateList uses the same title rule (it also refuses tabs and long titles now)
- tests: refused names, domains and titles, the accepted limits, nothing created for a bad title
- Parse the bounce as an RFC 3464 report: multipart/report with a
message/delivery-status (or message/global-delivery-status) part.
- Count a hard bounce only for a per-recipient block with Action: failed
and a status of 5.1.1, 5.1.2, 5.1.3, 5.1.6 or 5.1.10.
- Policy and content rejections (5.7.x), full mailboxes (5.2.x), delays,
4.x.x and Status lines in plain text or quoted text no longer count.
- Tests with real-looking DSNs for each class, quoted text and multiple
recipient blocks; the VERP token check is unchanged.
routes() is now the single table New registers, so a route added later is
covered by TestEveryRouteNeedsTheToken without editing it.
- api: declare the routes in one table (routes) and register from it
- api: table test walks it, 401 without a token, not 401 with one
- foreign_keys, busy_timeout(5000) and WAL now come from the DSN, not from
an Exec on one connection
- test: every connection of a 2-connection pool, in memory and on disk