release: 2.10.0: inbound-upstream-result - the upstream's answer in the Inbound log

Cut at the owner's word (2026-10-16): "потом режь" after the check, which he allowed ("Отправляй"). Inbound › Log says what became of accepted mail - queued, held, sent, deferred, bounced - with the upstream's last reply, the host and when (5348330, 295d72e, 46b90d2 design and plan; d515493 code, the reviews' findings fixed in it). Migration 0012, schema 12. On the test server as 2.9.1-post.d515493 (the same code), 2026-10-16: healthy, every program RUNNING, keys unchanged, schema 12. One message sent from the server to its own port 25 for selfpost@dev.mixdep.ru: its row sent, "250 2.0.0 Ok: queued as 04F0D1023EF" from mc-ent.mixfed.ru. (The owner's own message had gone to mc-ent directly: SelfPost is dev.mixdep.ru's second MX.) CHANGELOG [2.10.0]; pins in deploy/docker-compose.yml, README and the guide (pin, build, the sample restore message); development's "from pin" and row 32; roadmap row and recommended order; plan closed. No tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 17:03:38 +03:00
parent d51549385b
commit f4f6e0f23d
7 changed files with 23 additions and 13 deletions
@@ -5,6 +5,12 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); version

 ## [Unreleased]

+## [2.10.0] - 2026-10-16
+
+Inbound › Log says what became of accepted mail: the upstream's answer,
+its last reply and the host that gave it. Migration `0012`; schema 12.
+Nothing for an operator to do.
+
 ### Added

 - **Inbound › Log shows what the upstream answered** (inbound-upstream-result,
@@ -112,8 +112,8 @@ outbound mail will not reach the real internet without DNS, PTR, and port 25.
 > local image and pulls nothing:
 >
 > ```sh
-> docker build -f build/Dockerfile --build-arg VERSION=2.9.1 \
->   -t ghcr.io/mixeme/selfpost:2.9.1 .
+> docker build -f build/Dockerfile --build-arg VERSION=2.10.0 \
+>   -t ghcr.io/mixeme/selfpost:2.10.0 .
 > ```

 ```sh
@@ -122,7 +122,7 @@ docker run --rm -d --name selfpost-try \
  -e SELFPOST_HOSTNAME=mail.local.test \
  -e PANEL_COOKIE_SECURE=false \
  -v selfpost-try-data:/data \
-  ghcr.io/mixeme/selfpost:2.9.1
+  ghcr.io/mixeme/selfpost:2.10.0
 ```

 **Get the setup URL** (pick one):
@@ -23,7 +23,7 @@

 services:
  selfpost:
-    image: ghcr.io/mixeme/selfpost:2.9.1
+    image: ghcr.io/mixeme/selfpost:2.10.0
    restart: unless-stopped
    environment:
      SELFPOST_HOSTNAME: "${SELFPOST_HOSTNAME:?set the mail/panel hostname, e.g. mail.example.com}"
@@ -107,7 +107,7 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 2. Git tag `vX.Y.Z` and publish the GitHub Release only on explicit request (see
   [§ Release image](#release-image)).

-**Planned version cuts** (from pin `2.9.1`; adjust if semver changes mid-track):
+**Planned version cuts** (from pin `2.10.0`; adjust if semver changes mid-track):

 | Stage | ID | Cut |
 |---|---|---|
@@ -142,6 +142,7 @@ than the default «meaningful step» rule in [§ Commits and release build](#com
 | 29 | panel-dkim-signing | `2.8.0` |
 | 30 | dns-record-collapse, settings-save-row, notification-mail-recheck; `/data/opendkim` removed | `2.9.0` |
 | 31 | log panes wrap on a phone | `2.9.1` (PATCH) |
+| 32 | inbound-upstream-result | `2.10.0` |

 Docs-only prep (checklists in plans, no product code) uses the same per-step
 commit rule but **no** version cut until the next product stage ships.
@@ -204,14 +204,14 @@ cat ./data/setup-token
 #### Fixed image tag

 `deploy/docker-compose.yml` pins an explicit version (`ghcr.io/mixeme/selfpost:X.Y.Z`),
-deliberately never `:latest`. The current pin is `2.9.1`. **No 2.x image is
+deliberately never `:latest`. The current pin is `2.10.0`. **No 2.x image is
 published on ghcr.io yet** (the newest there is `1.3.0`); until one is, build
 it from the checkout under the pinned name, and Compose uses the local image
 instead of pulling:

 ```sh
-docker build -f build/Dockerfile --build-arg VERSION=2.9.1 \
-  -t ghcr.io/mixeme/selfpost:2.9.1 .
+docker build -f build/Dockerfile --build-arg VERSION=2.10.0 \
+  -t ghcr.io/mixeme/selfpost:2.10.0 .
 ```

 `VERSION` must equal the tag: it is the version the backup check compares
@@ -944,7 +944,7 @@ A version mismatch at step 5 refuses to start and leaves `/data` untouched —
 the panel exits with a message naming the tag to use, e.g.:

 ```
-backup: this backup was created by SelfPost 2.9.0 but this image is 2.9.1 — restore into the matching image (selfpost:2.9.0)
+backup: this backup was created by SelfPost 2.9.1 but this image is 2.10.0 — restore into the matching image (selfpost:2.9.1)
 ```

 Fix the tag in `docker-compose.yml` (build that tag as under [Fixed image
@@ -1,6 +1,6 @@
 # inbound-upstream-result

-**Status:** agreed 2026-10-16; one stage, `2.10.0`.
+**Status:** shipped `2.10.0` (2026-10-16).

 ## Problem

@@ -94,4 +94,7 @@ finding became:
 - [x] e2e: a relayed message's row shows `sent` with the sink's `250`; an
  upstream that refuses connections shows `deferred` with the reason.
 - [x] Docs. *Done (2026-10-16), with the reviews' findings above.*
- [ ] Roll out, read the server's journal; cut `2.10.0`.
+- [x] Roll out, read the server's journal; cut `2.10.0`. *Done (2026-10-16): on the
+  test server as 2.9.1-post.d515493, a message to selfpost@dev.mixdep.ru through
+  port 25 - its row sent, mc-ent.mixfed.ru's "250 2.0.0 Ok: queued as
+  04F0D1023EF" on it.*
@@ -28,7 +28,7 @@ in `git log` and [CHANGELOG.md](../CHANGELOG.md).

 | ID | Topic | Status | Progress | Plan |
 |---|---|---|---|---|
-| inbound-upstream-result | Inbound › Log shows what the upstream answered: sent, deferred, bounced, with its last reply | agreed (2026-10-16); built, unreleased | 6/7 | [plans/inbound-upstream-result.md](plans/inbound-upstream-result.md) |
+| inbound-upstream-result | Inbound › Log shows what the upstream answered: sent, deferred, bounced, with its last reply | shipped `2.10.0` | 7/7 | [plans/inbound-upstream-result.md](plans/inbound-upstream-result.md) |
 | health-setup-checks | Server › Health also checks the certificate's name, Postfix's greeting and the trusted proxy (was preflight) | agreed (2026-10-13) | — | — |
 | test-email | Send a test message from the panel (was preflight) | agreed (2026-10-13) | — | — |
 | inbound-antispam-panel | Inbound antispam journal + allow/deny lists | shipped `2.1.0` | 12/12 | [plans/inbound-antispam-panel.md](plans/inbound-antispam-panel.md) |
@@ -65,7 +65,7 @@ stages 1 and 2 as `2.5.0` the same day, stage 2b as `2.5.1`, stage 2c as
 `2.6.0` the same day; stage 6 (documents and tests, no cut) closed the
 audit. Of the three rows from [own-mta-builds](#own-mta-builds),
 **port25-bare-newline** shipped as `2.6.1` the same day and
-**base-trixie** as `2.7.0`, and **panel-dkim-signing** as `2.8.0` (2026-10-16). **dns-record-collapse**, **settings-save-row** and **notification-mail-recheck** shipped together as `2.9.0` the same day, with `/data/opendkim` removed as panel-dkim-signing planned. What is agreed after it is marked so in the index; every other
+**base-trixie** as `2.7.0`, and **panel-dkim-signing** as `2.8.0` (2026-10-16). **dns-record-collapse**, **settings-save-row** and **notification-mail-recheck** shipped together as `2.9.0` the same day, with `/data/opendkim` removed as panel-dkim-signing planned, then `2.9.1` (log panes on a phone) and **inbound-upstream-result** as `2.10.0`. What is agreed after it is marked so in the index; every other
 remaining item is a candidate. panel-docs shipped in
 [CHANGELOG.md](../CHANGELOG.md) `[1.8.0]`; dmarc-reports in `[1.7.0]`
 (its ingest path first ran in `2.0.0` and was reviewed on 2026-10-11, see