Persist before sending
Keep the message and intended delivery as application state.
Home / Product / Outbound mail
Send communication reliablyQueue outbound messages as stored work, record every attempt, retry eligible deliveries, and retain a sent copy.
A provider can time out after accepting a message. Persist the message before delivery and retry eligible attempts according to the queue policy. Store delivery state and attempt history so operators can choose the correct retry and customer response.
Daptin can write outbound messages to an outbox, process pending work through a scheduled action, record attempts, and calculate later retries. In clustered operation, shared claims reduce duplicate processing.
A successful sender path can also add the message to Sent. Show operators message state, attempt history, provider responses, and idempotency context for public mail delivery.
Keep the message and intended delivery as application state.
Store provider responses, attempt timestamps, recipient context, and next retry state with each message.
Retry pending work on a schedule with duplicate-reduction controls.
A single send can create several independent deliveries, each with its own successful result or next attempt.
Outbound mail does more when it can reuse the records, people, access rules, and workflows already in your application.
Build the message directly or from a template.
Store it in the outbox with its mail-server relationship.
A scheduled processor claims and sends eligible work.
Record delivered state or store the provider response and next retry time.
Start from the experience you want to create; the backend capability supports the work behind it.
Send confirmation or recovery mail with visible delivery work.
Queue status changes or reports produced by an action.
Create a message from application state and retain attempt evidence.
These capabilities share the same application context, so each one makes outbound mail more useful.
Design idempotent product messages and record every public mail delivery attempt. Teams define idempotency, retry, bounce, suppression, reputation, and customer communication policy.
Run Daptin locally, explore the live administration surface, and follow one complete application path.