mixandClaude Opus 5.5
ac985d03a8
Following the design commit df96690.
- Two columns (owner, 2026-10-14): sender_check_days.messages (migration
0009, not deployed) holds the messages deferred mid-message, from
cleanup's warning; deferred stays the connections smtpd turned away.
AddSenderCheckDeferred takes which; the counter passes cleanup's as a
message. The card has "Connections turned away" and "Messages deferred";
it warns on either within 24 hours (one mark, as before).
- Supervisord silent at start: postfixStarted asks again every 2 s for 30 s
(postfixState: started, running, known). With no answer the downtime is
the time since the alive mark - an upper bound - booked with estimated = 1
(sender_check_days.estimated, MAX over a day); the card prefixes such a
period's time with "≈ " and its note says what ≈ means. Before, such a
start counted nothing and the number the owner decides by read low.
- Help topic sender-check and the log topic word for word as the mockup
(help.go).
Tests: store (connections and messages apart, a period with an estimated
day); logtail (cleanup's warnings are messages); cmd/panel (supervisord
silent: the time since the mark, estimated); view fixture and the Health
page at four columns with ≈; e2e reads the row's two counts (panel down:
connections; panel hung: messages). Schema at 0009 with the columns.
schema-migrations row 9, CHANGELOG [Unreleased], audit plan lines ticked
(two), roadmap 28/62.
Evidence: go vet ./... clean; go test of store, view, cmd/panel ok locally,
logtail but for the Windows-only test; the server run follows before the
push.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
25 lines
1.6 KiB
SQL
25 lines
1.6 KiB
SQL
-- What Postfix wrote about a refusal (audit 2026-10-12, stage 2b). A message
|
|
-- the journal milter refuses at MAIL FROM - a level-2 limit, a client address
|
|
-- off the application's list - has no queue id, and Postfix's one line about
|
|
-- it, "NOQUEUE: milter-reject: MAIL from ...", was nowhere the message's page
|
|
-- could find it. The log tailer puts it on the row it belongs to. A message
|
|
-- refused for its From: line has a queue id (cleanup gives one before the
|
|
-- headers are judged), and its lines are found by it like any other's.
|
|
-- DDL only; a row written earlier has '' and says so on its page.
|
|
ALTER TABLE send_log ADD COLUMN refusal_line TEXT NOT NULL DEFAULT '';
|
|
|
|
-- A refusal row the panel did not get to write - the sender check answers 550
|
|
-- and writes the row a moment later, and a panel stopped in between wrote
|
|
-- none - is written by the log tailer from Postfix's line about it, and marked
|
|
-- so: recovered = 1.
|
|
ALTER TABLE send_log ADD COLUMN recovered INTEGER NOT NULL DEFAULT 0;
|
|
|
|
-- The Sender check card counts two things apart (the owner, 2026-10-14):
|
|
-- deferred stays the connections Postfix turned away while the check did not
|
|
-- answer, and messages are those deferred in the middle, when the check
|
|
-- stopped answering after a message had begun (cleanup's warning). estimated
|
|
-- marks a day whose downtime was taken from the alive mark alone, because
|
|
-- supervisord could not say at start since when Postfix ran: an upper bound.
|
|
ALTER TABLE sender_check_days ADD COLUMN messages INTEGER NOT NULL DEFAULT 0;
|
|
ALTER TABLE sender_check_days ADD COLUMN estimated INTEGER NOT NULL DEFAULT 0;
|