queue-table: Outbound › Queue as the drawn table, Inbound › Queue built
Owner, 2026-10-18: "Фиаско, что очередь не была сделана. Как мы это допустили? Исправляем!" The mockups out-queue and in-queue (design629de5e, guards8525e8e). - postfix: postqueue -j gives each message's size and each recipient's delay_reason (src/postqueue/showq_json.c, format_json(): "delay_reason" only when LEN(why) > 0); QueueListing reads it with the page's 5 s, QueueMessages keeps the notifier's 30 s. - view: one Queue page type for both directions (queue.go), one polled box (queue_body.html): a row per recipient, oldest first, cut at 200 with a foot; the head "N messages · size", "Refreshes on its own" while empty; Last reply is the delay reason, or where the message is (active, hold, incoming) before there was one. Inbound has no Details: an inbound message has no page of its own. - handlers: one read of the queue, split by the recipient's domain against the inbound domains; an outbound recipient is linked to its send-log row (store.SendLogRefsByQueueID, through idx_send_log_queue_id, plan pinned in TestSendLogQueriesUseTheirIndexes), matched without regard to case, else the message's first row. Both pages are the global role's; the inbound one 404s with the relay off. Routes /inbound/queue (+ /fragment), menu, touch menu and sibling strip. - Overview: Queues · Both empty · outbound and inbound with the relay on. - Help: the queue topic rewritten, an Inbound queue topic (word for word with the mockup; domain administrators do not see it, as with the lists). - TestUnbuiltScreensAreOnTheRoadmap and its rule in development.md: an exempted screen must be named in roadmap.md; queue-table leaves the roadmap; guide, architecture, panel-redesign.md updated. Tests: go vet; go test ./internal/web/... ./internal/store ./internal/postfix ./internal/notify pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,6 +5,32 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Inbound › Queue** (`/inbound/queue`, global role, with the inbound relay
|
||||
on): mail accepted on port 25 that its upstream has not yet taken, a row
|
||||
per recipient with the upstream's last reply - the screen `in-queue`, drawn
|
||||
for 2.0 and not built until now. Help has its topic.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Outbound › Queue is the table the mockup draws** instead of
|
||||
`postqueue -p`'s text: a row per recipient, oldest first - queue id, when
|
||||
it arrived, sender, recipient, and the last reply of the receiving server
|
||||
or why no connection was made - with *Details* to the message in the
|
||||
Outbound log when it has a row there. The box head counts the messages and
|
||||
their size; past 200 recipients the oldest 200 are listed and a line says
|
||||
how many wait. Read from `postqueue -j` (Postfix 3.10.13,
|
||||
`src/postqueue/showq_json.c`: `message_size`, and a recipient's
|
||||
`delay_reason` when it has one). A recipient of an inbound domain is on
|
||||
Inbound › Queue instead.
|
||||
- **Overview's queue card** is *Queues*, "Both empty", "outbound and inbound"
|
||||
while the inbound relay is on, as the mockup has it: Postfix keeps one queue
|
||||
for both.
|
||||
- `TestUnbuiltScreensAreOnTheRoadmap`: a screen the guards let pass unbuilt
|
||||
must be named in `docs/roadmap.md`. The two queues had been deferred on
|
||||
2026-10-09 with no roadmap row and were forgotten; development.md says so.
|
||||
|
||||
## [2.15.0] - 2026-10-18
|
||||
|
||||
The two proposals the security audit left as product choices. Migration
|
||||
|
||||
Reference in New Issue
Block a user