Write the S/MIME position down #273

New Issue

Closed

opened 2026-09-04 06:19:30 +00:00 by jcoffey-dev · 0 comments

jcoffey-dev commented

2026-09-04 06:19:30 +00:00

Owner

S/MIME was backlogged in conversation on 2026-08-27 and recorded nowhere in the repository — not ROADMAP.md, FEATURES.md, KNOWN-ISSUES.md, the README, or docs/. That is the state a plan is in just before it is forgotten, and it is also the state that lets the same probing get done a second time.

The entry says plainly that it is backlogged rather than refused, names #67 as the starting point — a working x:PublicKey manager, closed unmerged on 2026-08-26, none of which is in the tree today — and carries the findings that cost real probing:

encryptionAtRest is a field on x:AccountSettings, not an object of its own; there is no x:EncryptionAtRest whatever the docs suggest
it is self-service, no administrator involved
ordinary users can write their own x:PublicKey entries, despite the permissions table listing every sysPublicKey* permission as admin-only
Stalwart parses key material itself and returns a precise complaint, so a client should surface the server’s message rather than invent one

Dated to the live 0.16.19 they were taken against and marked as not re-run since the 0.16.20 upgrade — the same convention KNOWN-ISSUES.md uses for its own entries.

The one-way-door caveat is last on purpose: turning encryption-at-rest off does not decrypt what is already there, which is the part a user cannot undo by changing their mind.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JPKEqe6qBzFiyj8abT3z5a

Merged 2026-09-03 as coffey-labs/ihasmail@1f8c12e29e

_{Rebuilt from: git history, session transcript.}

S/MIME was backlogged in conversation on 2026-08-27 and recorded **nowhere in the repository** — not `ROADMAP.md`, `FEATURES.md`, `KNOWN-ISSUES.md`, the README, or `docs/`. That is the state a plan is in just before it is forgotten, and it is also the state that lets the same probing get done a second time. The entry says plainly that it is backlogged rather than refused, names [#67](https://github.com/Coffey-Labs/ihasmail/pull/67) as the starting point — a working `x:PublicKey` manager, closed unmerged on 2026-08-26, none of which is in the tree today — and carries the findings that cost real probing: - `encryptionAtRest` is a **field on** `x:AccountSettings`, not an object of its own; there is no `x:EncryptionAtRest` whatever the docs suggest - it is self-service, no administrator involved - ordinary users **can** write their own `x:PublicKey` entries, despite the permissions table listing every `sysPublicKey*` permission as admin-only - Stalwart parses key material itself and returns a precise complaint, so a client should surface the server’s message rather than invent one Dated to the live **0.16.19** they were taken against and marked as not re-run since the 0.16.20 upgrade — the same convention `KNOWN-ISSUES.md` uses for its own entries. The one-way-door caveat is last on purpose: turning encryption-at-rest off **does not decrypt what is already there**, which is the part a user cannot undo by changing their mind. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01JPKEqe6qBzFiyj8abT3z5a **Merged** 2026-09-03 as coffey-labs/ihasmail@1f8c12e29eed <sub>Rebuilt from: git history, session transcript.</sub>

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coffey-labs/ihasmail-github-archive#273