Keep sending with Postmark. 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 Postmark setup.
Postmark
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/postmark/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through Postmark. Tatami only reads the events it reports.
Password resets, receipts, and account updates need a clear delivery history when a customer reports a missing message. Tatami connects to Postmark webhooks and keeps bounce types, descriptions, tags, and message stream details together, helping your team investigate failures without treating every bounce as the same kind of problem.
Review delivery and bounce records with the Postmark message identifier, subject, and description where available. Give support and engineering a concrete starting point for the investigation.
Tatami maps transient and soft-bounce types to deferred outcomes. Inspect those separately from hard bounces, blocked messages, and other permanent failure classifications.
Retain Postmark's MessageStream, Tag, and custom metadata with events. Use these details to understand whether a problem concerns a specific stream, message category, or customer.
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 Postmark webhook at Tatami. Your mail keeps sending the same way.
Create a Postmark source in your Tatami project and copy the generated webhook URL. Name the source for the Postmark server or sending environment you are connecting.
In the relevant Postmark message stream, add a webhook using the Tatami URL. Enable Delivery, Bounce, Spam Complaint, and Subscription Change events, then save the configuration.
Use Postmark's webhook testing tools and send a test message. Confirm delivery and bounce details appear in Tatami, including the message stream and any custom metadata you supply.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
No. Tatami uses Postmark's bounce type. HardBounce and BadEmailAddress become bounced outcomes, while Transient, SoftBounce, and DnsError become deferred outcomes. The original type and description remain part of the event context.
Yes. Tatami retains custom Metadata supplied by Postmark along with native fields such as Tag and MessageStream. Include customer, campaign, or category identifiers when sending so delivery problems have useful context when you review them.
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 Postmark events arrive in minutes.