From 466a3d2089072b415cae5526d8cc3f909ba6b638 Mon Sep 17 00:00:00 2001 From: Mix Date: Thu, 15 Oct 2026 22:48:05 +0300 Subject: [PATCH] plan: panel-dkim-signing - Q1 decided, the signer on sockets of its own Co-Authored-By: Claude Opus 5.5 --- docs/plans/panel-dkim-signing.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/plans/panel-dkim-signing.md b/docs/plans/panel-dkim-signing.md index 8247b38..59b002b 100644 --- a/docs/plans/panel-dkim-signing.md +++ b/docs/plans/panel-dkim-signing.md @@ -2,7 +2,7 @@ **Status:** draft, 2026-10-15 - the row is agreed (owner, 2026-10-15, the order port25-bare-newline -> base-trixie -> panel-dkim-signing); three -questions below are open and go to the owner one at a time. +questions below go to the owner one at a time; Q1 is decided. **Date:** 2026-10-15 **Version:** `2.8.0` MINOR (after base-trixie's `2.7.0`). No migration; nothing for an operator to do. @@ -106,6 +106,7 @@ Decided here (technical, the owner may overrule): through, not a missing login, decides that the server's key may sign it; the sender check stays a header-only milter; and moving the signer into a process of its own later is a change of where it is started. + **Decided (owner, 2026-10-15): (a).** - **Q2. The key directory's name.** `/data/opendkim/keys//.private` stays as it is, or becomes `/data/dkim/...` (the entrypoint moves the tree once; KeyTable and SigningTable are deleted). A backup restores