Email delivery monitoring
Delivery monitoring that starts with the SMTP response.
Monitor acceptance, deferrals, bounces and complaints separately. See SMTP codes, enhanced status, MX hosts and provider trends without an invented deliverability score.
A dashboard that says “delivered” without showing the remote response is not monitoring. Transmitly records what happened at each stage: accepted, attempted, deferred, delivered to MX, bounced or complained.
Acceptance and delivery are different events
An API 202 means Transmitly committed the message. It does not mean the remote mail exchanger accepted it. Keeping those states separate makes the timeline readable: you can see whether a message is waiting, retrying, accepted by the remote server, or suppressed before an attempt.
What to watch
Use rates, not a single reputation number. Deferral pressure, hard-bounce rate, complaint rate and queue age answer different questions. A provider-specific deferral spike often means a throttle; a cross-provider spike points to your queue, DNS or content.
- SMTP code and enhanced status for every attempt.
- MX host and provider, so one bad route is visible.
- Attempt count and next retry time, without hiding the reason.
- Delivered-to-MX rate, separate from inbox placement.
- Complaint and bounce sources, including DSN and ARF.
Alerts should point to evidence
A useful alert names the provider, scope, time window and observed change. It should not say “deliverability dropped.” Transmitly opens incidents from policy-driven thresholds and keeps the evidence attached to the proposal and control action.
What we do not publish
We do not infer inbox placement from an SMTP 250. We do not combine unrelated signals into a made-up deliverability score. If a metric is unavailable, the dashboard says so instead of filling the gap.
Questions
Common questions
+Does delivered to MX mean the email reached the inbox?
No. It means a remote mail exchanger returned a 2xx response for the recipient. Inbox placement requires separate seed testing or receiver-side data.
+Can I see the exact SMTP failure?
Yes. Each attempt records the SMTP code, enhanced code, MX host and a sanitized reason. You can filter by provider and stream.
+Do you support webhooks for monitoring?
Yes. Delivery events are signed, retried, dead-lettered and replayable. Domain scoping lets you send only the domains an endpoint should receive.
+How long are metrics retained?
Message bodies and content-bearing events follow plan retention. Delivery metadata and audit records are kept longer for operations and billing.
Related
See what the remote MX actually said.
Start free, verify a domain and send a test. Acceptance and delivery evidence stay separate.