Receive mail for application accounts
SMTP delivery resolves configured users and mailboxes before accepting and storing messages.
Mail server
Make email part of the application.
Run mail accounts and mailboxes, accept SMTP delivery, read mail through IMAP, and send product messages from backend actions.
- SMTP
- IMAP
- Outgoing queue
Built into the data layer
Received mail can start an application action.
Daptin stores mail in application tables, making messages available to APIs, permissions, administrative tools, and custom actions.
Use standard mail clients
IMAP exposes stored mailboxes to compatible readers and tools.
Send from backend operations
Actions can prepare outbound messages for product notifications and workflow communication.
Retry temporary delivery failures
The outgoing queue records each attempt and schedules another attempt after a temporary failure.
Where it earns its place
Keep product email close to product state.
Transactional notifications
Send confirmations, assignments, approvals, and status changes from the same actions that understand the underlying record.
Inbound workflows
Turn mail delivered to a known application account into data that APIs and actions can process.
Team mailboxes
Give support or operations teams a standard IMAP view while the application keeps the message history available to its own logic.
Your own domains
Operate mail for product identities you control instead of making a third-party inbox the system of record.
Delivery guarantees
A mail server still needs mail-server operations.
Daptin connects SMTP receipt, IMAP access, stored messages, and an outbound queue. Delivery retries provide at-least-once behavior; recipients can still receive duplicates, so downstream processing should be idempotent.
Production mail also depends on TLS, DNS, sender reputation, relay restrictions, and correct domain records. Daptin supplies the application integration—not a shortcut around operating internet email responsibly.