Keep sending with PostShiba. 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 PostShiba setup.
PostShiba
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/postshiba/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through PostShiba. Tatami only reads the events it reports.
When your product sends email for several customers, a delivery problem needs more context than a total bounce count. Connect PostShiba delivery webhooks to Tatami to review rejected recipients, temporary delays, and dropped messages alongside the account and campaign details included in your events.
Review deferred events and their delivery responses when receipts, account notifications, or other time-sensitive messages are taking longer to reach the receiving server.
Include account, site, and campaign identifiers in PostShiba unique arguments. Keep that context with the event so your team can investigate the affected customer or message type.
Inspect dropped messages and spam reports alongside successful deliveries. Use the supplied reasons to decide whether to review recipient data, sending practices, or a particular campaign.
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 PostShiba webhook at Tatami. Your mail keeps sending the same way.
Create a project in Tatami, add a PostShiba source, and copy the webhook URL. Give the source a name that identifies the sending account you want to monitor.
Open Delivery webhooks in PostShiba and create an endpoint using the Tatami URL. Subscribe to delivered, bounce, deferred, dropped, spamreport, and unsubscribe events, then save the endpoint.
Send a test message and confirm its delivery event appears in Tatami. Include account, site, campaign_id, and category in unique arguments when you need that context for investigations.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
Use the outbound delivery-event webhook. PostShiba inbox webhooks report incoming mail and serve a different purpose. Tatami monitors delivery, bounce, deferral, drop, complaint, and unsubscribe events from your outgoing messages.
Add account and site identifiers through unique arguments, along with campaign_id or category where useful. For SMTP sends, use X-Capsule-Unique-Args. Avoid using tenant_id for your own identifier: PostShiba supplies its tenant slug in that field.
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.
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 PostShiba events arrive in minutes.