Keep sending with Mandrill. 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 Mandrill setup.
Mandrill
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/mandrill/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Mandrill. Tatami only reads the events it reports.
Mandrill, also known as Mailchimp Transactional, reports delivery problems through message-event webhooks. Tatami organizes those outcomes with diagnostic text, bounce details, and message metadata. Investigate temporary deferrals separately from hard bounces and rejections when a receipt, password reset, or other application email fails to arrive.
Tatami maps Mandrill soft_bounce and deferral events to deferred outcomes, while hard_bounce and reject events become bounced. Review the diagnostic evidence for each kind of failure.
Review reject events alongside bounce descriptions and SMTP diagnostics when supplied. Identify which application messages need investigation before attempting another send.
Add tenant and campaign values to Mandrill message metadata. Tatami retains supported identifiers with delivery events so support and engineering can investigate the same affected traffic.
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 Mandrill webhook at Tatami. Your mail keeps sending the same way.
Create a Mandrill source in Tatami and copy its webhook URL. Name it for the Mailchimp Transactional account or application whose email you want to monitor.
In Mailchimp Transactional Settings, add a webhook with the Tatami Post To URL. Select delivered, deferral, hard_bounce, soft_bounce, reject, spam, and unsub events, then save it.
Use the webhook's Send Test action and confirm the selected outcomes appear in Tatami. Follow with an application email to verify that your own metadata accompanies real events.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
This page covers Mandrill, the Mailchimp Transactional service, and its message-event webhooks. Configure the webhook in your Transactional account. A Mailchimp Marketing audience webhook is a different integration and is not the connection described here.
They become deferred outcomes, as do deferral events. Hard bounces and rejections become bounced outcomes. Tatami preserves available diagnostics and bounce descriptions so your team can inspect the actual reason instead of relying only on the normalized status.
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 Mandrill events arrive in minutes.