Commit Graph
7 Commits
Author SHA1 Message Date
Truespar Team 7d2bc7059f Ship a Windows binary, release 0.1.3
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.
2026-08-24 08:48:26 +02:00
Truespar Team 1168974409 Single-source the version
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.
2026-08-24 07:58:57 +02:00
Truespar Team 6ea08a8790 Document two missing endpoints, fix README counts
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.
2026-08-24 07:53:23 +02:00
Truespar Team 18c80ddf70 license: dual-license MIT OR Apache-2.0, and ship third-party notices
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.
2026-08-24 07:44:05 +02:00
Truespar Team 8c17d32abb ci: publish a multi-arch image so the quickstart stops compiling
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.
2026-08-24 00:03:07 +02:00
Truespar Team a234f8931d docs: describe the inbound webhook payload as it actually is
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.
2026-08-23 23:52:46 +02:00
Truespar Team 0727e3319e Initial public release
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.
2026-08-23 23:44:38 +02:00