inbound-provider-imap
Registers the "imap" provider for inbound-mail-foundation using imapflow — password/app-password auth covers classic IMAP hosts without any OAuth (plus an XOAUTH2 fallback consuming an access token from the secret slot). Incremental sync via a UIDVALIDITY:lastUid cursor (UIDVALIDITY change triggers a cursor-invalid full resync), initial backfill bounded by the foundation backfill window, and live push via IMAP IDLE for the watch supervisor. Store the per-account connection JSON (host/port/secure/user/password) in the account credential secret slot before the first sync.
How it fits
Section titled “How it fits”What this feature needs to run (Requires).
flowchart TB
n_inbound_provider_imap["inbound-provider-imap"]
subgraph how_reqs["Requires"]
n_inbound_mail_foundation["inbound-mail-foundation"]
n_secrets["secrets"]
end
n_inbound_mail_foundation --> n_inbound_provider_imap
n_secrets --> n_inbound_provider_imap
Dependencies
Section titled “Dependencies”- Requires:
inbound-mail-foundation,secrets - Activation: always on (not toggleable)
Extensions & cross-feature APIs
Section titled “Extensions & cross-feature APIs”- Registers extension:
inboundMailProvider→imap