jcoffey-dev
cc6f1eb298
Everything clients, users and operators meet now carries the fork's name, with no aliases (SPEC.md §2.4, changed here from "protocol identifiers stay"): - JMAP: upstream's registry capability is urn:inbuxa:jmap:registry, beside the fork's own urn:inbuxa:jmap. - WebDAV lock and sync tokens are urn:inbuxa:dav*; clients resync once. - Sieve: vnd.inbuxa.while and vnd.inbuxa.expressions. sieve-rs spells these into its compiler, so it's vendored (vendor/sieve-rs, 0.7.3) and patched in; a unit test fails if Cargo.lock ever moves past the vendored copy. The trusted runtime now names itself too, rather than answering sieve-rs's default. - The web interface's OAuth client is inbuxa-webui. On every start the old stalwart-webui client is removed and any application naming it is moved over. - The spam filter's blobs are INBUXA_SPAM_*; every start moves any left under the old keys, so a trained model survives. - SQL stores and log files default to inbuxa, in the code and in the schema served to the admin (checksum regenerated). - Settings are INBUXA_* only. A STALWART_* variable that's set where its INBUXA_* one isn't stops the server at startup, naming it. - The version-upgrade messages link docs.inbuxa.org's migration page, and the OpenAPI description, smtp crate metadata and web-push test fixtures lose the name. Kept on purpose, allowlisted with reasons: the OAuth key-derivation contexts (renaming them would end every session and invalidate every sealed client id) and the hashed application prefix. Also fixes a latent start-up failure: ensure_client updated an existing first-party client with a revision of 0, which the registry's assertion never matches, so adding a redirect URI or changing the webmail secret failed start-up. And the principal session test now expects legacyProtocols (C-1, added 2026-09-21), which it had missed. Tested: the server builds without warnings; common's 106 unit tests, including the vendoring check; a new integration test for the two start-up migrations; and the webdav, jmap, imap and SMTP Sieve suites.
29 lines
1.6 KiB
Plaintext
29 lines
1.6 KiB
Plaintext
# String literals allowed to keep the upstream project's name.
|
|
# Read by tools/fork/name-check.py. One per line: path<TAB>literal as a JSON
|
|
# string, as `name-check.py --list` prints it. Each group says why it stays;
|
|
# add a line only under a reason, or with a new one.
|
|
#
|
|
# Everything clients, users and operators meet was renamed on 2026-09-22
|
|
# (docs/spec/SPEC.md §2.4, tools/fork/renames.py). What's left is invisible,
|
|
# or names the old spelling in order to retire it.
|
|
|
|
# Key-derivation contexts. Nobody sees them, and renaming them would
|
|
# invalidate every sealed OAuth token and client id already issued.
|
|
crates/common/src/auth/oauth/client_id.rs "stalwart-oauth-client-id-sw1"
|
|
crates/common/src/auth/oauth/token.rs "stalwart-oauth-token-sw1"
|
|
|
|
# Hashed before it's used as a blob key, so it never appears anywhere.
|
|
crates/common/src/manager/application.rs "STALWART_APP_"
|
|
|
|
# Pre-rename names, read only to retire them: the web interface's OAuth
|
|
# client (removed on start), the spam filter's blobs (moved to their new
|
|
# keys), and the environment prefix (refused with the variable to rename).
|
|
crates/common/src/manager/first_party.rs "stalwart-webui"
|
|
crates/migration/src/lib.rs "STALWART_SPAM_CLASSIFIER_MODEL.lz4"
|
|
crates/migration/src/lib.rs "STALWART_SPAM_TRAIN_DATA.lz4"
|
|
crates/types/src/branding.rs "STALWART"
|
|
|
|
# OPEN, not yet decided (2026-09-22): upstream's published spam-filter rules,
|
|
# which the server downloads at runtime from this address.
|
|
crates/registry/src/schema/structs_impl.rs "https://github.com/stalwartlabs/spam-filter/releases/latest/download/spam-filter-rules.json.gz"
|