From 8a0f21c1ddd58f658f33c62039b4a04784cf8e9e Mon Sep 17 00:00:00 2001 From: John Coffey Date: Sat, 14 Nov 2026 19:00:14 -0700 Subject: [PATCH 1/2] DMARC reports: "passed on one check alone" for partial passes "N of them with SPF or DKIM failing" read as a failure for mail that was delivered and passed DMARC. The count is unchanged; the per-sender lines and the explanation still say which check failed. Suggested in forum topic 232. --- src/features/incomingReports/DmarcSummaryCard.tsx | 4 ++-- src/i18n/en.json | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/features/incomingReports/DmarcSummaryCard.tsx b/src/features/incomingReports/DmarcSummaryCard.tsx index 1df96fb..7a4096c 100644 --- a/src/features/incomingReports/DmarcSummaryCard.tsx +++ b/src/features/incomingReports/DmarcSummaryCard.tsx @@ -132,8 +132,8 @@ function DomainBlock({ summary }: { summary: DomainSummary }) { {t('inReports.partialCount', { count: summary.partial, - defaultValue_one: '{{count}} of them with SPF or DKIM failing', - defaultValue_other: '{{count}} of them with SPF or DKIM failing', + defaultValue_one: '{{count}} passed on one check alone', + defaultValue_other: '{{count}} passed on one check alone', })} )} diff --git a/src/i18n/en.json b/src/i18n/en.json index 70cd10b..0423944 100644 --- a/src/i18n/en.json +++ b/src/i18n/en.json @@ -2142,8 +2142,8 @@ "empty": "No reports yet. Large providers send one a day for each domain whose DMARC record asks for them (rua=).", "partialSpf": "SPF failed on {{count}}", "partialDkim": "DKIM failed on {{count}}", - "partialCount_one": "{{count}} of them with SPF or DKIM failing", - "partialCount_other": "{{count}} of them with SPF or DKIM failing", + "partialCount_one": "{{count}} passed on one check alone", + "partialCount_other": "{{count}} passed on one check alone", "partialHint": "These still passed DMARC, because one passing check is enough. SPF failing is usual for forwarded mail, which keeps its DKIM signature. A sender of yours that always fails SPF may be missing from your SPF record, and DKIM failing on one route can mean a key that doesn’t match or a service that changes messages." }, "inTls": { -- 2.54.0 From 68dc0b5d7243d817e82e7b66b7f01b58971caaf8 Mon Sep 17 00:00:00 2001 From: John Coffey Date: Sat, 14 Nov 2026 19:02:19 -0700 Subject: [PATCH 2/2] CHANGELOG: 2026.10.26.6 --- CHANGELOG.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 992fb18..2e77e76 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,6 +14,17 @@ https://git.coffeylabs.org/inbuxa/inbuxa-admin/releases. Every version PR adds that version's entry here. CI refuses a version this file has no entry for (`tools/changelog-check.sh`). +## [2026.10.26.6] - 2026-11-15 + +A fix to the certificates guide for the 2026 series, the same as in +27.1-rc.8. + +### Fixed +- Certificates guide: adding a Let's Encrypt account no longer fails with + "Cannot modify server set property". The guide sent the account's + description, which only the server may set, so it could only switch domains + on servers that already had a matching account. (#205) + ## [27.1-rc.16] - 2026-11-14 Pairs with inbuxa-server 27.1-rc.22. -- 2.54.0