Email on Sentin8 — an SMTP/LMTP transfer engine, a mail & collaboration data core with JMAP, IMAP/POP3/Sieve/CalDAV access, and a TLS gate for the well-known ports.
Every service this vertical ships, each owning its own data and API surface.
The mail transfer engine: SMTP/LMTP protocol handling, the durable delivery queue (message + recipient state machine with scheduled retries), DKIM signing, DMARC/TLS-RPT report generation.
The mail plane's data core: mailboxes, messages, folders, contacts, calendars (the email8 schema) plus the JMAP API — the authenticated read/write surface for the other mail services.
The mailbox access protocols: IMAP (full CAPABILITY handling), POP3, ManageSieve, and the CalDAV/CardDAV/WebDAV collaboration endpoints — reading mail data through Store.
The raw-TCP front door for the well-known mail ports (SMTP submission 587, SMTPS 465, IMAPS 993, …): terminates the TLS/TCP listener set and discovers healthy MTA/Access instances at runtime.
User- and staff-facing applications, thin by design — tokens never reach the client.
Typed facades over every service API — the only supported integration surface.
Email8 inherits the Sentin8 security model and adds mail's own guarantees — authenticated access on every protocol, DKIM-signed outbound, and TLS-only listeners.
Store owns mailboxes, messages, folders, contacts, and calendars — MTA, Access, and Webmail all compose against it through authenticated APIs, never raw tables.
The MTA DKIM-signs every outbound message and generates DMARC/TLS-RPT reports — deliverability and domain alignment are built in.
IMAP with full CAPABILITY handling, POP3, ManageSieve, and CalDAV/CardDAV/WebDAV — every mailbox protocol served through one access tier.
Gate terminates the well-known mail ports (submission 587, SMTPS 465, IMAPS 993) with the platform's post-quantum certificates and discovers healthy instances at runtime.
The authenticated JMAP read/write surface powers Webmail and any third-party client — batched, efficient, and protocol-versioned.
Email8 contains no platform infrastructure of its own — identity, events, storage, and scheduling are consumed from the platform.