The intended retrieval API will offer one secure message shape across official Gmail, Microsoft Graph, and standards-based IMAP connectors while keeping provider truth available.
DewEngine does not yet retrieve production mailboxes. The target is a hosted connection followed by account-scoped list and get operations, with real provider conformance required before any connector is sold.
A list request should support account, container, time, participant, unread, and attachment filters; return an opaque cursor; and provide summary fields without automatically downloading every message body.
A message detail request should return normalized headers, text and HTML alternatives, attachments, and raw provider extensions according to the connected account's granted scopes and the application's own authorization.
Every response should make account health and last successful sync visible. Products need to distinguish current data from a mailbox that is reconnecting, rate-limited, or awaiting a full resync.
Where the provider supplies it and permissions allow it, raw MIME can be exposed as an optional representation. The common response should remain parsed and provider-neutral.
No. The intended design lists attachment metadata first and retrieves binary content only when requested.
Not yet. Gmail, Microsoft Graph, and IMAP/SMTP connectors are planned. This guide documents the intended architecture and the provider requirements a production release must satisfy.
DewEngine is in development. Real use cases decide what ships first.