rspamd and mailpit tracked `latest`, so the stack you got depended on the
day you pulled it and dependabot had nothing to raise a pull request
against. Pinned at 4.2.2 and v1.31.6, and NATS moved 2.11 -> 2.15 while
I was in there.
publish.yml still said main was validated by ci.yml, which is gone.
scripts/check.sh and scripts/e2e/run-e2e.sh are the gate, run before a
tag goes up.
MinIO's community edition was archived and its images withdrawn. Both
quay.io/minio/minio and quay.io/minio/mc now answer 401/404 to an
anonymous pull and they are off Docker Hub entirely, so `docker compose
up -d` could not fetch them and the quickstart was broken for anyone
without a local cache.
`weed mini` is master, volume server, filer and S3 gateway in one
process. It takes its admin identity from AWS_ACCESS_KEY_ID /
AWS_SECRET_ACCESS_KEY and creates the bucket named by S3_BUCKET, so the
mc one-shot goes away - and ensure_bucket() in sentio-storage already did
that job anyway. Its S3 port, 8333, is the one config/default.toml has
always pointed at.
e2e: 19/19 against it, including the attachment round-trip and raw .eml
archival through the store.
Two things the security work needs to land cleanly here.
The startup gate and migration 002 cannot both hold on a first run: the
migration seeds a publicly-known admin key, the gate then refuses to
start, and there is no way to rotate a key through an API that will not
boot. docker compose up -d crash-looped, and the e2e harness could not
authenticate. The evaluation stack now sets
SENTIO_ALLOW_BOOTSTRAP_KEY=1 with the reason written next to it, and the
README gives the rotate-then-remove sequence. A manual install gets no
exemption, which is where the gate matters.
The README's rotation snippet also said data.key; the field is
data.raw_key, and the bootstrap key's id is the same well-known UUID as
the admin tenant.
Drops .github/workflows/ci.yml: this repository has no hosted CI by
decision, and scripts/check.sh is the gate. Worth noting what that
costs - the seven repo-layer isolation tests skip unless DATABASE_URL is
set, so nothing runs them automatically.
Review pass 1 (architectural) follow-ups on top of the previously
addressed CRITICAL create/inbound-route IDORs:
- #9 smtp-credential create: unique-violation (23505) now maps to
SentioError::Conflict -> ApiError::Conflict -> HTTP 409 instead of an
opaque 500; message names the taken username.
- #6 bootstrap-key gate now fails CLOSED: a database error during the
startup check refuses to start (was: debug! + continue, letting a
transient outage defeat the gate). SENTIO_ALLOW_BOOTSTRAP_KEY=1
remains the explicit recovery hatch.
- #7 README documents the refuse-to-start behavior, the recovery hatch,
and the manual SQL rotation path (API rotation is impossible when the
server won't bind).
- #8 migration 003 raises a NOTICE per renamed credential so operators
see which SMTP usernames stop authenticating (breaking change).
- #5 new GitHub Actions workflow (ci.yml): postgres service container,
migrations + full workspace tests + explicit tenant-isolation suite —
the regression tests previously skipped silently without DATABASE_URL
and nothing ran them.
- #11 tests clean up their tenant rows (cleanup_tenant) and a unit test
pins the handler-level guard contract: mismatched path tenant must
serialize as 404 (concrete assert on the response status).
- migration 004 extends error_events.error_type CHECK with 'conflict'.
cargo test --workspace --all-targets: 744 passed, 0 failed.
Removes .github/workflows/ci.yml. Everything it ran lives in
scripts/check.sh instead: fmt, clippy, tests, release build, cargo-deny,
the third-party notices diff and the OpenAPI spec diff. It reports every
failure in one pass rather than stopping at the first.
publish.yml stays - that builds and publishes releases on a tag, which
is not a check.
Contributing guide and pull request template now say plainly that
nothing runs these for you.
CI triggered on both push to any branch and pull_request, so every branch
ran twice and main ran again after merge. Push is limited to main now, and
a concurrency group cancels superseded runs. publish gets a group too, but
never cancels - a half-published release leaves a manifest without its
binaries.
Adds a pre-push hook installer for fmt and clippy.
The image now carries both binaries, so the release job lifts sentio-mcp
out of it the same way and no second set of release builds is needed.
Each gets its own archive: an MCP client host does not want the mail
server, and vice versa.
Notices are generated with --workspace now. Without it cargo-about
crawls only the root package, so rmcp and schemars would ship
unattributed.
Windows compiles green in CI, so the release now carries a third
platform. It needs a real cargo build on a Windows runner rather than
the image-extraction path the Linux binaries use, so it is its own job
feeding the release, and SHA256SUMS is computed once all three are in
place.
Release notes say plainly that Linux is the supported target and the
Windows build is compiled but not exercised in CI.
Pin cargo-about, split the install into its own step so a failure is
attributable, and print the diff plus upload the generated file when it
mismatches. The check has failed three runs and the logs need admin
rights to read.
Compile-only. The code already has a non-unix shutdown path and no
unix-only deps; the open question is whether aws-lc-sys builds there.
If this stays green, shipping Windows binaries is a small step.
Relicensed so a recipient may take whichever terms suit them. That is
strictly more permissive than either alone: MIT for the simplest terms
and GPLv2 compatibility, Apache-2.0 for the explicit patent grant some
adopters require. It also matches the Rust norm - 255 of the 517
dependencies are exactly this pair.
Distributing binaries is what makes attribution an obligation rather
than a courtesy. The repository alone redistributes nothing, since
dependencies are fetched at build time, but the container image and the
release tarballs contain compiled third-party code, and MIT and BSD both
require their notices to travel with it. 76 crates are MIT-only.
THIRD-PARTY-NOTICES.md is generated by cargo-about from the resolved
graph for the two targets actually shipped, and now lands in
/usr/share/doc/sentio in the image and inside each tarball.
deny.toml existed but nothing ran it, and it would have failed
immediately: the allow list omitted licences already present (0BSD,
MIT-0, Unlicense, CDLA-Permissive-2.0, BSD-1-Clause) and it used the
pre-2.0 schema. Rewritten against what the graph actually contains, and
wired into CI alongside a staleness check on the notices.
Running it surfaced six advisories, none of which appear exploitable
here, all recorded with reasons rather than silenced:
- rsa 0.9 carries Marvin (RUSTSEC-2023-0071), a timing sidechannel in
private-key operations. The crate is used in one place, generating a
DKIM keypair. No decryption, no oracle. There is no fixed release.
- h2 0.3 and rustls-webpki 0.101 come through aws-smithy-http-client's
legacy hyper 0.14 stack, so they sit on the path to the object
store. Sentio's own listeners and delivery client are on rustls
0.23. Getting the AWS SDK off its legacy client is follow-up work.
- rustls-pemfile is unmaintained, not vulnerable.
Publishing ran on every push to main and moved `latest` with it, so a
first-time user following the README got whatever landed on main an hour
ago rather than a release. `latest` now means the latest release,
because publish.yml only runs for a v* tag. Pushes to main are still
validated by ci.yml, which builds the image without pushing it.
metadata-action switches to latest=auto, so v1.0.0 moves `latest` and
v1.1.0-rc1 does not.
Adds a release job that creates the GitHub Release with tarballs for
linux/amd64 and linux/arm64 plus a SHA256SUMS file. The binaries are
lifted out of the images built moments earlier rather than compiled
again: it avoids a second pair of ten-minute release builds, and it
guarantees the tarball holds the same bytes the container runs. Since
`docker create` never executes anything, the arm64 image unpacks on an
amd64 runner without emulation - verified locally, both extract as
correct ELF binaries for their architecture.
The notes state a glibc floor of 2.34, which is what the binaries
actually import; the earlier draft said 2.36 and undersold which distros
can run them.
The quickstart told people to run `up -d --build`, which is a release
build of thirteen crates before they can see anything work. That is a
poor first impression for software whose whole pitch is that it is easy
to run. `docker compose up -d` now pulls ghcr.io/truespar/sentio.
Each architecture is built on its own native runner - amd64 on
ubuntu-latest, arm64 on ubuntu-24.04-arm - and the two are merged into
one manifest afterwards. The obvious alternative, one buildx job with
both platforms, cross-builds arm64 under QEMU, and a Rust release build
under emulation runs for well over an hour. arm64 matters here because
most people trying this on a laptop are on Apple silicon.
Tags: latest on main, sha-<short> always, and semver on v* tags so a
deployment can pin. GHCR needs no credentials beyond GITHUB_TOKEN.
docker-compose.build.yml keeps the from-source path for anyone changing
the code, and the image name is unchanged between the two so nothing
else in the stack cares which produced it. CI's docker job now runs on
pull requests only, since main is covered here.
Verified locally through the build overlay: image builds, stack comes
up, e2e passes 9/9.
Sentio SMTP: self-hosted, multi-tenant email infrastructure in Rust.
Gives an AI agent its own real email address. Inbound mail arrives
parsed, authenticated and spam-scored as a webhook; replies go out
DKIM-signed over the same REST API. Full SMTP on both sides, with
DKIM/SPF/DMARC/ARC, MTA-STS, DANE and a three-tier anti-spam pipeline.
Apache-2.0.