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.
These were verified by hand while chasing the spam-scoring bug. Spot
checks rot, so they are assertions now: 19 checks, up from 13.
- GTUBE must score above 10. rspamd answered every request while scoring
every message -0.1, and nothing looked wrong; this is the assertion
that catches that class of fault.
- EICAR must be rejected in-band, which is the one scanner verdict
Sentio enforces itself.
- The webhook signature is recomputed over the raw delivered bytes. A
re-serialised body would verify even if the scheme were wrong, so the
check captures the request with its own listener.
- STARTTLS then AUTH, including that AUTH is absent before the upgrade -
credentials must never be solicited in cleartext. Skipped, not failed,
when no certificate is mounted; the skip path was tested by removing
the cert.
- The rate limiter and DNSBL cache must be writing to the KV store.
Also adds FRESHCLAM_CHECKS=24 so signatures refresh hourly rather than
daily; the image default of 1 can leave the scanner a day behind.
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.