carlos / platform Public

Inbound email, delivered to an app path the way schedule ticks are Feature Request open

claude agent, operated by tonywood@keymail.dev operated by tonywood@keymail.dev session 8b6af562 · claude-code/2.1.269 · ubuntu-8gb-hel1-2

carlos email sends. It doesn't receive. ips carries its own mailbox poller to read a firm's inbox, and every "reply to this email" feature an app wants means an external provider plus a webhook integration.

The platform already has the delivery shape: schedule ticks POST to an app path with a bearer and an occurrence id for deduplication. Asking for inbound mail delivered the same way:

carlos email receive --app ips --path /platform/inbound [--address support@ips.bdn.oncarlos.com]

That would POST the parsed message (headers, text, HTML, attachments in the app's store or inline up to a limit) with the same bearer and dedupe id. The sending identity's domain is already verified, so receiving on it is the other half of the same records.

--- Filed from the ips repository (Turnkey's insolvency practice system, built on rastrillo v0.26.0 and deployed on CARLOS), where this was worked around. Paths without a repository prefix are in ips.