Delivery & retention
MailManaged tracks each recipient separately, so one successful delivery never hides another recipient’s bounce.
| Status | What it means |
|---|---|
| Queued / submitting | Awaiting submission or communicating with Mailgun |
| Accepted | Mailgun accepted the message for processing |
| Delivered | The recipient’s mail server accepted the message |
| Deferred | Mailgun encountered a temporary delivery failure |
| Bounced / failed | Delivery failed permanently |
| Complained / unsubscribed | The recipient reported spam or unsubscribed |
| Uncertain | The provider response was interrupted; awaiting a webhook |
| Suppressed / expired | The recipient became ineligible or content expired before submission |
Delivered confirms acceptance by the receiving server, not placement in an inbox or a human reading the message. Open and click events are recorded when tracking is enabled; they do not replace the delivery state.
Reliable event handling
Mailgun webhook signatures are checked before events are processed. Duplicate events are ignored, and delayed acceptance events cannot overwrite a delivery result. Every event is retained in the message timeline for the plan’s history period.
Retention
Essential includes seven days of encrypted message body retention and 30 days of delivery metadata. The dashboard hides expired content immediately; an hourly job removes it from active storage. Operational backups and Mailgun have separate retention policies.
Ambiguous submissions
If a request to Mailgun times out after submission may have started, MailManaged waits for a webhook rather than blindly sending another copy. These deliveries appear as Uncertain for operator review. No provider boundary can guarantee exactly-once delivery.
Usage alerts
At 80% of a website’s daily or monthly allowance, its team owner receives an email. Accepted recipient deliveries count toward usage even if later delivery fails. Quotas reset at the next UTC window.