Standards-based connection
Describe the supported account path and project scope clearly before configuration begins.
Standards-based email architecture
Use a standards-based mailbox path without hiding operational state.
Model mailbox configuration, sync health, folder state, and account recovery as visible product concerns instead of integration afterthoughts.
Email connection architecture
Set up IMAP with a clear product boundary.
Make account ownership, project context, health state, and recovery visible to the customer instead of burying the integration behind an opaque setup step.
Credential recovery boundary
Treat connection degradation as a customer recovery problem with a controlled route, not a reason to reveal or copy provider credentials.
The product workflow
IMAP should be visible in the product, not hidden behind a connection status.
Explore the original Moira surfaces for the path from a customer-controlled connection to an observable workflow, with capability and recovery context alongside it.
1 of 3
Connection control plane
Give the customer a real surface for operating IMAP.
Moira keeps connected-account health, project-scoped credentials, delivery evidence, and a safe recovery route together in the customer console.
Explore the product
Use cases
IMAP product use cases
Use the provider as part of an ATS, CRM, or outreach workflow while retaining project and capability context at every step.
MMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
ATS publisher
Keep IMAP connection context beside candidates, account health, and recruiter-owned recovery actions.
Explore use caseMMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
CRM publisher
Put IMAP activity alongside the customer record so account teams can investigate the next safe action.
Explore use caseMMaya ChenConnection context updated
DDaan BakkerHealth state needs review
AAmara SinghProject event observed
Outreach publisher
Make IMAP a visible, policy-aware stage in a controlled multi-step outreach workflow.
Explore use caseDeveloper integration
Make the IMAP event contract explicit before it drives an action.
Associate each signal with a project, account, provider state, and recovery path. The result is an operable integration rather than a disconnected API response.
Read developer documentationconst event = await moira.events.verify({
projectId, provider: "imap",
eventId: request.headers.get("x-moira-event-id"),
});
if (event.state === "attention_required") {
await queueRecoveryReview(event);
}Trust work in progress
Security and compliance status
These are current in-progress programs, not completed certifications, compliance guarantees, or a substitute for your own assessment.
Integration questions
IMAP integration FAQ
Answers describe product boundaries and operational recovery without making provider capability promises.
How does a IMAP connection begin?
A workspace member begins in the intended project context. Moira presents only the connection path and account state that the live provider registry and workspace policy permit.
Does this page guarantee a IMAP capability?
No. The page describes an integration architecture. Actual availability remains subject to configured provider paths, account state, entitlement, project policy, and provider terms at the time of use.
How does the customer recover a degraded connection?
The customer console is designed to present account health, the specific recovery route, and the relevant project context. Operators should follow that route rather than retrying a blind action.
How are events and delivery outcomes represented?
Moira keeps provider outcomes and event references available beside the workflow so a product can distinguish requested, observed, and attention-required states.
What data boundary applies to this provider?
Configuration and account state remain in the approved connection boundary. Moira shows the customer enough state to recover a route without exposing connection material.
How are webhooks and retries handled?
Event-oriented integrations should retain an identifier, delivery boundary, and retry context. Downstream systems should decide on recovery from evidence instead of replaying an uncertain operation.
What is Moira’s current security and privacy posture?
Moira is progressing through a SOC 2 Type II audit and an ISO 27001 certification program, while operating a GDPR-focused privacy program. These are in-progress initiatives, not completed certifications or a guarantee of suitability for a particular use case.
Where should an engineering team start?
Start by defining project scope, the customer-owned connection path, event contract, and recovery model. Then use the customer console and developer documentation to check live readiness.
Provider path
How the provider path stays operable
A useful integration does not stop at authorization. It makes the current boundary, account state, and recovery route legible inside your product.
IMAP workflowIllustrative
- Show mailbox health before a workflow silently fails
Expose a clear account signal and the next action for the customer or support operator who owns the connection.
- Keep mailbox structure legible inside the product
A connected account can be understood as a scoped mailbox context rather than a generic transport abstraction.
- Resolve configuration changes with a named next step
Use account state to explain whether a customer should reconnect, review settings, or request help.
Start with the right boundary
Connection modes
Standards-based connection
Describe the supported account path and project scope clearly before configuration begins.
Credential recovery boundary
Treat connection degradation as a customer recovery problem with a controlled route, not a reason to reveal or copy provider credentials.
Product workflows
From connection to an operable outcome
Sync health
Show mailbox health before a workflow silently fails
Expose a clear account signal and the next action for the customer or support operator who owns the connection.- Visible account state
- Project-specific health
- Recoverable failure path
IMAP account Health visible
Connection stateObserved
Project boundaryScoped
Recovery routeReady
Folder projection
Keep mailbox structure legible inside the product
A connected account can be understood as a scoped mailbox context rather than a generic transport abstraction.- Scoped mailbox context
- Operationally useful events
- Support diagnostics
IMAPContextEvents
01
Connected account context attached
02
Workflow event ready for review
03
Recovery state is visible
Account recovery
Resolve configuration changes with a named next step
Use account state to explain whether a customer should reconnect, review settings, or request help.- No plaintext secret display
- Clear ownership
- Auditable resolution
IMAP event stream
Account state projected
evt_01Event envelope received
evt_02Delivery evidence recorded
evt_03Capability boundaries
Capability map
Every category communicates its readiness state in words, not colour alone.
Account operations
- Connection status projection
- Project-scoped recovery
- Operational diagnostics
Mailbox workflow
- Configured mailbox routing
- Provider-aware state
- Customer-controlled action boundary
Event evidence
- Normalized state changes
- Webhook delivery context
- Account audit trail
Build with context
Developer resources
Keep connection state, event evidence, and security boundaries in the implementation path from the start.
IMAP connection architectureStart with project context, the hosted connection route, and an explicit account-health state.Event delivery and recoveryUse signed webhook delivery, event identifiers, retries, and account state to make failures actionable.Connection security boundaryKeep credentials, provider consent, API-key scope, and project isolation separate from browser-visible code.
Data-handling boundaryConfiguration and account state remain in the approved connection boundary. Moira shows the customer enough state to recover a route without exposing connection material.
Architecture questions
Frequently asked questions
How does a IMAP connection start?
A workspace member initiates a connection in the intended project context. Moira presents only the authorization path and capability state that the control plane permits.
What happens when mailbox configuration or account health changes?
The account health and capability state becomes visible in the customer console. A customer or operator can follow the specific reconnect, approval, or policy-recovery route instead of retrying a blind action.
Is availability guaranteed by this page?
No. This page explains the integration architecture. The live provider registry, workspace policy, and provider terms decide whether a connection or action is available at execution time.
Start with verified readiness