mirror of
https://github.com/truespar/sentio.git
synced 2026-11-17 16:17:37 +00:00
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.