Keep sending with Postal. 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 Postal setup.
Postal
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/postal/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Postal. Tatami only reads the events it reports.
Running Postal gives you control of your mail infrastructure and responsibility for understanding delivery problems. Tatami turns Postal message-status webhooks into a focused view of sent, delayed, held, and failed messages. Review the details and server output attached to events when troubleshooting your own sending environment.
Tatami records MessageHeld and MessageDelayed as deferred outcomes. Review Postal's status details and output to understand why a message has not completed delivery.
Review MessageDeliveryFailed alongside MessageBounced events. Use original message identifiers and sender context to connect a failure with the application that sent the message.
Inspect subject, sender, recipient domain, and message tags when Postal includes them. Those details help narrow an investigation after a configuration change or an unexpected rise in failures.
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 Postal webhook at Tatami. Your mail keeps sending the same way.
Add a Postal source to your Tatami project and copy the webhook URL. Use a source name that identifies the Postal server you operate.
Open the server's Webhooks settings in Postal and add the Tatami URL. Select MessageSent, MessageDelayed, MessageDeliveryFailed, MessageHeld, and MessageBounced, then save the webhook.
Send a test email through that Postal server and check Tatami for its Sent outcome. Inspect the event details and verify that the expected sender and message information are present.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
MessageSent becomes delivered. MessageDelayed and MessageHeld become deferred. MessageDeliveryFailed and MessageBounced become bounced. Tatami retains the Postal payload so you can inspect the original status and available details while investigating.
This integration focuses on message delivery outcomes. Postal DomainDNSError notifications are not retained as delivery events in Tatami. Continue using Postal's domain configuration and DNS checks when diagnosing SPF, DKIM, or other domain setup issues.
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 Postal events arrive in minutes.