inbuxa/inbuxa-server
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 3 Wiki Activity
Files
ce6882fe93e0c3d836ea7dc76bcb4bd951b520b3
inbuxa-server/vendor/sieve-rs/CHANGELOG.md
T
jcoffey-dev cc6f1eb298
ci / fork-checks (pull_request) Successful in 16s
Details
ci / build (pull_request) Successful in 7m53s
Details
Rename the identifiers that carried the upstream name 
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.
2026-09-22 19:33:02 -07:00

1.4 KiB
Raw Blame History

sieve-rs 0.7.3

  • Bump mail-builder dependency to 0.5.

sieve-rs 0.7.2

  • Fix: replace action adds additional From header.

sieve-rs 0.7.1

  • Bump fancy-regex dependency to 0.17.0.
  • Fixed rkyv serialization lifetimes for rustc 1.93.0.

sieve-rs 0.7.0

  • Added rkyv support.
  • Bump mail-parser dependency to 0.11.0.
  • Fix: Allow redirect to sender (#11).

sieve-rs 0.6.0

  • Replaced phf with hashify.
  • Bump mail-parser dependency to 0.10.0.

sieve-rs 0.5.3

  • Fixed register_match_var function.

sieve-rs 0.5.2

  • Fixed set_global_variable function.

sieve-rs 0.5.1

  • Case insensitive envelope tests (#6).
  • Set envelope variables internally (#10).

sieve-rs 0.5.0

  • Removed context.

sieve-rs 0.4.0

  • Support for expressions.

sieve-rs 0.3.1

  • Bump mail-builder dependency to 0.3.0.

sieve-rs 0.3.0

  • Updated execute grammar.
  • Upgraded to latest mail-parser.
  • Envelope accessible from environment variables.

sieve-rs 0.2.0

  • Improved event loop.

sieve-rs 0.1.0

  • Initial release.
Reference in New Issue View Git Blame Copy Permalink