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 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.
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.