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:
@@ -863,7 +863,7 @@ only reads (the delete confirmation at `GET …/delete` renders a form).
|
||||
| Outbound › Log, Queue | `GET /outbound/log` · `/outbound/log/fragment` · `/outbound/log/{id}` · `GET /outbound/queue` · `/outbound/queue/fragment` |
|
||||
| Outbound › DMARC reports | `GET /outbound/dmarc` · `…/dmarc/domains/{id}` · `…/dmarc/reports/{id}` — registered only with `DMARC_REPORTS_ENABLE=true` |
|
||||
| Inbound › Domains | `GET, POST /inbound/domains` · `/inbound/domains/{id}` · `POST …/dns-recheck`, `…/upstream`, `…/recipients` · `GET, POST …/delete` — registered only with `INBOUND_RELAY_ENABLE=true` |
|
||||
| Inbound › Log, Filter lists | `GET /inbound/log` · `GET, POST /inbound/filter-lists` · `POST /inbound/filter-lists/{id}/delete` — registered only with `INBOUND_RELAY_ENABLE=true` |
|
||||
| Inbound › Log, Queue, Filter lists | `GET /inbound/log` · `GET /inbound/queue` · `/inbound/queue/fragment` · `GET, POST /inbound/filter-lists` · `POST /inbound/filter-lists/{id}/delete` — registered only with `INBOUND_RELAY_ENABLE=true` |
|
||||
| Server | `GET /server/health` (+ `/fragment`) · `POST /server/health/recheck`, `/server/health/reload`, `/server/health/test-message` · `GET /server/log` (+ `/fragment`) · `GET, POST /server/backup` · `POST /server/backup/import` · `/server/users`, `…/new`, `…/{uid}`, `…/{uid}/delete` · `GET, POST /server/settings` · `POST /server/settings/dns-recheck` · `GET /server/components` |
|
||||
| Account | `GET /account` · `POST /account/profile`, `/account/password`, `/account/email/confirm` |
|
||||
| User menu | `GET /help` · `POST /logout` (public mux) |
|
||||
|
||||
@@ -451,6 +451,15 @@ that changes the mockups, a guard or the script touches nothing else under
|
||||
[plans/panel-redesign.md](plans/panel-redesign.md) § The contract and
|
||||
§ Enforcement have the full rules.
|
||||
|
||||
**A drawn screen that is not built has a row.** A screen the mockups draw and
|
||||
the panel does not build, or builds otherwise (the guards' `deferredScreens`
|
||||
and `outlineExempt`), is named in [roadmap.md](roadmap.md) - a row of the index,
|
||||
or an idea under *Ideas* - in the same commit that exempts it.
|
||||
`TestUnbuiltScreensAreOnTheRoadmap` fails otherwise. The queue as a table and
|
||||
the Inbound queue were drawn for 2.0, deferred on 2026-10-09 with no row of
|
||||
their own, and then forgotten for nine releases, the guards green because they
|
||||
had been told to be (owner, 2026-10-18: "Фиаско"); built in `2.16.0`.
|
||||
|
||||
### End-to-end (container suite)
|
||||
|
||||
Separate Go module `test/e2e/`; **not** included in the main module's
|
||||
|
||||
+14
-3
@@ -447,7 +447,7 @@ changes.
|
||||
|---|---|---|
|
||||
| Overview | Overview | `/overview` |
|
||||
| Outbound | Domains · Log · Queue · DMARC reports | `/outbound/domains`, `/outbound/log`, `/outbound/queue`, `/outbound/dmarc` |
|
||||
| Inbound | Domains · Log · Filter lists (global role) | `/inbound/domains`, `/inbound/log`, `/inbound/filter-lists` |
|
||||
| Inbound | Domains · Log · Queue and Filter lists (global role) | `/inbound/domains`, `/inbound/log`, `/inbound/queue`, `/inbound/filter-lists` |
|
||||
| Server | Health · System log · Backup · Users · Settings | `/server/health`, `/server/log`, `/server/backup`, `/server/users`, `/server/settings` |
|
||||
| User menu (your name) | Account · Help · Sign out | `/account`, `/help`, `POST /logout` |
|
||||
|
||||
@@ -564,14 +564,25 @@ past that the page shows the last result). *Greeting* is the `220` line Postfix
|
||||
### Queue and System log
|
||||
|
||||
- **Outbound › Queue** (`/outbound/queue`, global role) — live view of
|
||||
messages Postfix is still trying to deliver, deferring or holding, as
|
||||
`postqueue -p` lists them. It only shows: nothing there deletes or forces a message. A box
|
||||
messages Postfix is still trying to deliver, deferring or holding, 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
|
||||
(from `postqueue -j`). *Details* opens the message in the Outbound log when
|
||||
it has a row there; the panel's own mail and bounces have none. The box
|
||||
head counts the messages and their size; past 200 recipients the oldest 200
|
||||
are listed and a line says how many there are - `postqueue -p` in the
|
||||
container lists them all. It only shows: nothing there deletes or forces a message. A box
|
||||
states this instance's retry policy — first retry delay, later backoff cap,
|
||||
how long a message stays in the queue — from `postconf -h`, read once when
|
||||
the panel starts. A `postconf -e` override inside the container is visible
|
||||
after the next panel (or container) restart. There is no maximum attempt
|
||||
count: Postfix retries until the message is delivered or the queue lifetime
|
||||
runs out.
|
||||
- **Inbound › Queue** (`/inbound/queue`, global role, with the inbound relay
|
||||
on) — the same Postfix queue, the recipients of inbound domains: mail
|
||||
accepted on port 25 that its upstream has not yet taken, with the
|
||||
upstream's last reply. A recipient belongs here when its domain is an
|
||||
inbound domain, and to Outbound › Queue otherwise.
|
||||
- **Server › System log** (`/server/log`) — tail of `/data/log/mail.log`
|
||||
(Postfix and related daemon lines). The log rotates daily (14 files kept)
|
||||
with a `postfix reload` after each rotation; a background loop checks every
|
||||
|
||||
@@ -95,7 +95,7 @@ only.
|
||||
| Outbound: domain, applications, settings, log, DMARC | all domains | assigned outbound domains |
|
||||
| Inbound: domain (upstream, recipients), log | all domains | assigned inbound domains |
|
||||
| Add / delete a domain, either direction | yes | no |
|
||||
| Queues, either direction | yes | no, until the queue is a filterable table |
|
||||
| Queues, either direction | yes | no — the queue is the instance's; a domain's rows for its administrator would be a decision of its own |
|
||||
| Inbound › Quarantine | all domains | assigned inbound domains |
|
||||
| Inbound › Filter lists, Server › Preflight | yes | no — the lists are instance-wide |
|
||||
| Account, Help | yes | yes |
|
||||
@@ -215,8 +215,10 @@ Rules that come with the rename:
|
||||
**Needs its own roadmap decision before it is built** (the mockups show the
|
||||
target; none of this is smuggled in with the restyle):
|
||||
|
||||
- Queue as a table — parse `postqueue -j` instead of printing `postqueue -p`.
|
||||
- Inbound queue — the same queue filtered by recipient domain.
|
||||
- Queue as a table — parse `postqueue -j` instead of printing `postqueue -p`
|
||||
(built in `2.16.0`).
|
||||
- Inbound queue — the same queue filtered by recipient domain (built in
|
||||
`2.16.0`).
|
||||
- Inbound log — rides on `inbound-antispam-panel` (`2.1.0`).
|
||||
- Server › Health — a route for the tables removed from Overview, and the
|
||||
home of *Reload configuration* (today a card on `/status`).
|
||||
@@ -236,7 +238,6 @@ Drawn and not built (`deferredScreens` in the guard tests):
|
||||
|
||||
| Screen | Item | State |
|
||||
|---|---|---|
|
||||
| `in-queue` | [queue-table](../roadmap.md#queue-table): the queue as a table from `postqueue -j`, and an Inbound › Queue | undecided; Outbound › Queue shows postqueue's listing in a log pane (`outlineExempt`) |
|
||||
| `in-quarantine`, `in-quarantine-message` | inbound-quarantine, an idea off the roadmap ([its notes](inbound-quarantine.md)) | its open questions stay open; the mockup assumes SelfPost-held mail, release to upstream, 14 days, delegated like the rest of Inbound |
|
||||
|
||||
The sibling strip under the navbar holds five or six entries per group without
|
||||
|
||||
@@ -30,7 +30,6 @@ directory).
|
||||
|---|---|---|---|---|
|
||||
| security-audit-2026-10-17 | Stage H of the 2026-10-17 security audit: the test server's host (S1, S2, S5) and its DNS (S3) | stages 0-6 shipped `2.14.4`, the product side of S3 `2.15.0`; stage H the owner's | 27/29 | [security-audit-2026-10-17.md](security-audit-2026-10-17.md) § Stage H |
|
||||
| go-milter-upstream | An issue and a PR for go-milter: its header map outlives a message and is unbounded | prepared 2026-10-16, the owner posts | — | [third_party/go-milter/PATCHES.md](../third_party/go-milter/PATCHES.md) |
|
||||
| queue-table | Outbound › Queue as the table the mockup draws, from `postqueue -j`; an Inbound › Queue (`in-queue`) | candidate, undecided since 2026-10-09 | — | — |
|
||||
|
||||
After a context reset, pick an item marked `agreed` or `in progress`, then work
|
||||
the **Implementation checklist** in its linked plan. The `Progress` column above
|
||||
@@ -93,25 +92,6 @@ option), `third_party/go-milter` goes and `go.mod`'s `replace` with it.
|
||||
|
||||
---
|
||||
|
||||
## queue-table
|
||||
|
||||
**Problem:** the 2.0 mockups draw Outbound › Queue as a table and an
|
||||
Inbound › Queue (`in-queue`); the redesign kept both out as decisions of
|
||||
their own (owner, 2026-10-09). Outbound › Queue shows `postqueue -p`'s own
|
||||
listing in a log pane, and the mockup's `in-queue` is drawn but not built
|
||||
(`deferredScreens`, `outlineExempt` in the guard tests).
|
||||
|
||||
**Goal:** the outbound queue as a table from `postqueue -j` - a row per
|
||||
message with its sender, recipients, age and last reason - and, if the owner
|
||||
wants it, the same for mail port 25 holds for an upstream.
|
||||
|
||||
**Recommendation:** the outbound table first, read-only - about 4 h with its
|
||||
tests, since the notifier already reads `postqueue -j` for each message's
|
||||
arrival time; the inbound queue and any action on a row (retry, delete) only
|
||||
if the owner asks for them, each drawn mockup-first.
|
||||
|
||||
---
|
||||
|
||||
## Dropped, with the condition for return
|
||||
|
||||
Items the owner took off the roadmap. Each names what would bring it back;
|
||||
|
||||
Reference in New Issue
Block a user