Keep sending with KumoMTA. Tatami reads its delivery events and shows you what bounced, what got blocked, and what to fix next.
No DNS changes. No rerouting mail. See the KumoMTA setup.
KumoMTA
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/kumomta/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through KumoMTA. Tatami only reads the events it reports.
KumoMTA produces detailed delivery logs, but an incident often requires a shared view beyond an individual server. Connect KumoMTA log hooks to Tatami to investigate deliveries, transient failures, bounces, and expirations with queue, campaign, tenant, and response details when those fields are included in your logging configuration.
Review TransientFailure records as deferred outcomes. Inspect the recipient domain and response details to understand the remote delivery problems your KumoMTA instance is encountering.
Bring Bounce, Expiration, OOB, and AdminBounce records into one investigation. Preserve the original log context when determining why a message did not complete delivery.
Include tenant, campaign, and relevant message headers in log hooks. Review that context alongside delivery responses when several applications or customers share your KumoMTA infrastructure.
Tatami explains each bounce, watches your IPs and domains, and tells your team when something breaks.
1,240 Outlook bounces since 9:00, all from 198.51.100.24.
Microsoft is blocking that IP. Gmail and Yahoo look normal.
Also works in Claude Code and Codex through mcp.tatamimonitor.com.
Google, Yahoo, and Microsoft signals for every IP and domain.
Outlook is bouncing mail from 198.51.100.24 with 550 5.7.1 S3150.
Also sent to
Discord
Email
Rules on bounces, blocklists, volume, and throttling.
One filtered link per customer.
Point the KumoMTA webhook at Tatami. Your mail keeps sending the same way.
Add a KumoMTA source in Tatami and copy its webhook URL. Choose a name that identifies the cluster or environment sending your log events.
Follow KumoMTA's official Tatami Monitor integration guide to configure an HTTP log hook using the Tatami URL. Include the message headers and identifiers your team needs for investigations.
Reload your validated KumoMTA policy and send a test email. Confirm a Delivery event appears in Tatami and inspect the response and attribution fields in its event details.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
Yes. KumoMTA publishes a Tatami Monitor integration guide in its documentation. It explains how to forward log events to a Tatami source through an HTTP log hook. Use it alongside the setup instructions shown when you create your source.
Tatami maps TransientFailure and supported deferral records to deferred outcomes. Raw Reception, Delayed, and Rejection records are excluded by the current integration. Include the delivery-result records your team needs when configuring the log hook.
No. A delivery event means the receiving mail server accepted the message. It does not confirm whether it reached the inbox or spam folder. Tatami monitors the delivery events you send, bounce reasons, and sender reputation to help you investigate deliverability issues; it does not measure inbox placement.
Providers are unlimited on every plan. Connect the rest of your email stack the same way.
PostShiba deliverability tool
Amazon SES deliverability tool
Customer.io deliverability tool
Smartico deliverability tool
Bento deliverability tool
$10 per million emails. First 100 IPs free. See pricing
Connect the webhook and watch your first KumoMTA events arrive in minutes.