Ran them on a clean Ubuntu host. Steps 1, 2, 4 and 5 were correct;
the rest were not.
- PostgreSQL 18 is a hard floor because the schema calls uuidv7(), a v18
builtin. On 16 the migration dies with "function uuidv7() does not
exist", which explains nothing. Said so, with the symptom.
- Step 3 used createuser --pwprompt, which is interactive and never
mentioned that the password has to match database.url. Added the
scriptable form.
- Step 6 told you to run ./target/release/sentio-smtp and then setcap
/usr/local/bin/sentio-smtp, a path that does not exist until step 7.
- Step 7 could not work: the unit ran as User=sysop with
WorkingDirectory=/home/sysop/sentio and read
/etc/sentio/production.toml, none of which the README creates. It also
had redis-server in both Requires= and Wants= with contradictory
comments.
The unit now runs as a sentio user the README creates, reads the config
path step 5 writes, and separates hard dependencies from optional ones.
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.
The notices listed Sentio's own crates with their versions, so bumping
to 0.1.2 staled the file and CI caught it. That is the check working,
but it is a footgun: every version bump would break the build until
someone regenerated.
Marking the workspace publish = false and telling cargo-about to skip
private crates removes them entirely, which is also what a third-party
notices file should contain. The file no longer depends on our version.
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.
The banner printed CARGO_PKG_VERSION and the spec hardcoded 1.0.0, so
Cargo.toml said 0.1.0, the spec said 1.0.0 and the tag said 0.1.2. All
three now come from [workspace.package] version, and CONTRIBUTING says
to bump it before tagging.
send-multipart and dns-check are routed and served but were never
registered with utoipa, so the spec omitted them and a generated client
would have lost both. Spec is now 116 operations over 85 paths, matching
the 116 routed handlers.
Also: config table was missing 7 of the 20 sections, the top diagram is
mermaid so GitHub renders it properly, and the callout boxes are plain
prose.
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.
The README and the agent guide both said the payload arrives parsed,
with headers, bodies and attachments. It does not. InboundPayload in
crates/sentio-smtp-server/src/routing.rs is POSTed verbatim and carries
identity, envelope, spam_score/spam_action, llm_category/llm_summary,
threading, loop-guard headers, DSN parameters, and raw_eml_key.
No bodies. No attachments. Anyone writing a handler from the old text
would have gone looking for a body field and found nothing, which is the
worst kind of documentation error: confidently wrong about the first
thing a reader touches.
Both pages now show the real shape and point at GET
/v1/messages/{id}/raw and /attachments for the content, and say why the
split exists - a webhook that stays small regardless of a 25 MB
attachment, and a handler that only needs the spam verdict never moving
the body at all.
Two more details taken from the code rather than assumed:
- Route matching is exact, domain, regex or catch_all; first match
wins, and a regex that fails to compile is logged and skipped rather
than failing the delivery.
- Retry classification is 2xx delivered, 5xx/408/429 transient, any
other 4xx permanent, network errors transient - with retries
scheduled through the queue so they survive a restart. The
consequence worth stating for agent authors is that a handler
blocking on a model will time out, be classified transient, and earn
a duplicate.
The capabilities table said "parsed message data" too; corrected.
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.