Keep sending with Mailgun. 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 Mailgun setup.
Mailgun
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/mailgun/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Mailgun. Tatami only reads the events it reports.
Mailgun reports temporary and permanent delivery failures through its webhooks. Tatami keeps that distinction visible, turning temporary failures into deferred outcomes and permanent failures into bounces. Review the receiving server's response alongside your campaign and tenant metadata when troubleshooting a domain, an application notification, or a customer account.
Inspect the severity on Mailgun failed events. Tatami distinguishes temporary deferrals from permanent bounces so you can investigate delays separately from messages that will not be delivered.
Review delivery-status codes, descriptions, and MX host information when supplied. Keep the error evidence close to the affected domain and message instead of relying on a failure count.
Include tenant_id, campaign_id, and category_id in Mailgun user variables. Use that context to investigate whether a specific customer or message category is producing bounces or complaints.
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 Mailgun webhook at Tatami. Your mail keeps sending the same way.
Add a Mailgun source in Tatami and copy its webhook URL. Name it for the sending domain or account you plan to connect.
Configure Mailgun webhooks for delivered, temporary failure, permanent failure, complained, and unsubscribed events using the Tatami URL. Apply them at the domain or account scope you want to monitor.
Send a test email and inspect its delivery outcome in Tatami. Verify that failure events include severity and that your user variables appear in the event context.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
For a failed event, Tatami reads Mailgun's severity field. A permanent failure becomes a bounced event; other failure severities become deferred events. The original delivery-status details stay available for investigation.
Send campaign_id and other identifiers as Mailgun user variables. Mailgun's API uses the v: prefix, while SMTP supports the X-Mailgun-Variables header. Tatami extracts supported fields such as tenant_id, campaign_id, category_id, and ip_pool from those variables.
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 Mailgun events arrive in minutes.