Keep sending with GreenArrow. 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 GreenArrow setup.
GreenArrow
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/greenarrow/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through GreenArrow. Tatami only reads the events it reports.
A GreenArrow delivery attempt can succeed, fail, or defer. Tatami reads those statuses alongside bounce and complaint events so your team can investigate the delivery path with SMTP responses, MTA identifiers, and sending-IP context. Bring operational evidence from your GreenArrow infrastructure into a shared monitoring view.
Separate successful attempts from failures and deferrals. Tatami also treats connmaxout statuses as deferred, keeping temporary connection issues distinct from completed deliveries.
Inspect MTA identifiers, outbound IPs, MX hosts, and SMTP responses when supplied. Use those details to investigate the route involved in a delivery problem.
Review bounce_all, bounce_bad_address, and scomp events with their list, send, and campaign context. Give the team responsible for the audience concrete evidence to review.
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 GreenArrow webhook at Tatami. Your mail keeps sending the same way.
Create a GreenArrow source in Tatami and copy its webhook URL. Name the source for the GreenArrow instance or traffic group you are connecting.
Configure a JSON Event Notification System destination using the Tatami URL. Include delivery_attempt, bounce_all, bounce_bad_address, scomp, and engine_unsub; enable deferral and connmaxout statuses for delivery attempts.
Validate the GreenArrow configuration and send a test message. Check that its delivery-attempt outcome appears in Tatami with the expected MTA and SMTP-response details.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
No. Tatami reads the status: success becomes delivered, failure becomes bounced, and deferral, deferred, or connmaxout becomes deferred. The original status and SMTP response remain available with the event.
Enable delivery_attempt events and include deferral statuses in your GreenArrow event-delivery configuration. Tatami's setup instructions also include connmaxout. Without those statuses in the webhook feed, Tatami cannot report the corresponding attempts.
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 GreenArrow events arrive in minutes.