2 Commits

Include renames

Author	SHA1	Message	Date
mixandClaude Opus 5.5	b905f3e560	panel-notifications: Account, Server > Settings, Server > Health, help; e2e ... The pages of the mockups accepted in 87fa0a4, built from the kit's partials (written by a Sonnet agent into the working tree, reviewed here): - Account: "Send me notifications" in the Profile form, saved with the profile; an unticked box is off. - Server > Settings: the instance switch (box 03), and box 04 Notification mail with the DKIM and SPF records of the server's own name, drawn with the record partial of a domain's DNS page and checked in DNS. Sending rate limits are box 02 in the left column. A record that is not in place is tagged as a warning, not a failure: notifications are sent without it. - Server > Health: card 06 Notification mail with the state of each record and a link to Settings, beside Configuration (07); part of the polled fragment; Re-check DNS forces it too. Overview does not run this check. - help.go: the Notifications topic and the clauses in Settings and Your account, word for word with help.html. If the server's key cannot be read the pages still render: the DKIM record is left out and SPF is shown unchecked. e2e: the administrator gets a mailbox behind the sink and the server's DKIM record from Settings is published; the level-2 refusal of the next step must then arrive as a notification from postmaster@mail.e2e.test, signed as that name with the key Settings shows, and must not be a row of the Outbound log. The rotation step now waits for Postfix to be running: it follows a step that restarts the container, and logrotate's `postfix reload` failed in between. On the test server, for this tree: go vet clean, go test ./... 23 packages ok, make e2e ok (147 s); the notification reached the sink 28 s after the refusal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 16:21:48 +03:00
mixandClaude Opus 5.5	815236a607	delivery-log-storage: e2e holds the page to its lines after a rotation ... New step delivery_log_survives_rotation: the page of the first delivered message must list the line that opened its queue id and its delivery line, then mail.log is rotated with logrotate -f, the current file is checked to hold no delivery line, and the page must list both lines still. Before this feature the page searched the current file and would show none. The step runs after negative_level1_ratelimit: placed right after the first delivery it rotated away the "connect from" line the level-2 step reads from the current log, and that step failed. On the test server, for this tree: go vet clean, go test ./... 22 packages ok, make e2e ok (126 s). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 10:25:21 +03:00