2 Commits

Include renames

Author	SHA1	Message	Date
mixandClaude Opus 5.5	c171fb5bc7	from-header-binding: the sender check, what it costs, its pages; guide, architecture, security ... A message's From: line is held against the application that sends it, under the rule Postfix holds the envelope sender to. OpenDKIM chooses the key by that line, so until now an application could have mail signed as another domain of the server or as the server itself. The check (internal/milter/sender.go) - A role of the panel on a socket of its own (SENDER_CHECK_SOCKET), first in smtpd_milters and strict: default_action=tempfail. The journal milter keeps its socket and stays fail-open. postfix-wrapper waits for the new socket. - It reads no database: what an application may send as comes from Postfix's own sender_login_maps, what the server signs for from OpenDKIM's SigningTable. Both are read again when they change; one that cannot be read defers mail. - One From: field, one address, allowed by the envelope's lookup; then no other name of the SigningTable may appear anywhere in the raw line. Refused: 550 5.7.1 naming the line, reduced to printable ASCII. - A refusal is a send-log row with reason "from" and the header address (migration 0006), written by another goroutine and not waited for. The journal's refusals record their reason too (limit, client), and the notifier takes only a limit's. What it costs (docs/plans/from-header-binding.md, Statistics) - The role marks itself alive every 2 s; at start the gap since the mark is downtime, counted from Postfix's start if later and not at all when supervisord says Postfix is not running. - The log tailer counts the connections Postfix turned away: a warning that names the socket, then milter-reject "Service unavailable" from the same smtpd. Seen on the stand: the client is refused from CONNECT on and leaves at AUTH (454), so no MAIL line is ever written. - sender_check_days, a row per UTC day, kept a year. Pages - Health: the card "Sender check", the socket's row, and the cards layout - boxes numbered by importance in two stacks read in rows; the left stack polls, the three readings of the right one are swapped in by id. - Outbound log: a refused row says why in its tag (wrong From, wrong client, rate-limited); the message's page shows the From: line and what the application may send as. - Help: topic "Sender check", word for word the mockup's. Found by the stand, fixed here: the names for the second look came from the sender bindings, and a domain with a key and no application yet was not among them. e2e: negative_journal_milter_fail_open is gone - it proved that mail passes with the panel down, which is no longer so. In its place sender_check_holds_the_from_line (another domain's From:, the hostname's, a stranger's, an address off the list, another sender in the display name - refused; own addresses - delivered) and panel_down_defers_mail (4xx with the panel stopped, the container alive, mail again after, downtime and one deferred message on Health, the card warning). Test server, this tree before the last cosmetic edits (a fixture row, a fact's size, docs): go vet ok, go test 23 packages ok, make e2e ok (337 s). Locally after them: internal/web/view ok. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 19:35:43 +03:00
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