Access is invite-only during beta. Once invited, create a key to personalize these examples. Production sending requires a separate review.

Did they get the email?

Look up the address from the top bar. Read the three cards. Remove a suppression only when the customer asked.

Paste the address into Recipient lookup in the top bar.

  1. Last status, last seen, and whether they can receive. Can receive is no when a suppression or a firewall rule is in the way.
  2. Sends. The latest fifty faces for that address, with the same bounce explanation as Events. Paste the explanation. Do not ask for a raw payload dump. A Dropped face means we never queued the message. Common Dropped reasons: the address is on suppressions, the firewall blocked it, or the account still needs production approval.
  3. Suppressions. Why the address is blocked, and a link to the causing event when we have one.
  4. Firewall. The matching check, if we blocked the address before send.

When to Remove

Use Remove only if the customer asked to receive mail again, and only after you read the reason. Bounce, spam report, and unsubscribe are usually a hard stop. A manual row can come off if they asked. Viewer cannot Remove. Support and Team Administrator can.

Who can do this

Anyone who can open Events can look up a recipient. Support and Team Administrator can remove a suppression. Viewer can read the page and cannot remove. Support sees the classified explanation, not a raw payload dump.

About

PostShiba is the email platform that powers Bento behind the scenes. You can build your own products, like Bento, on top of it.

© 2026 PostShiba by Backpack Internet Pty. Ltd. All rights reserved.

The same policies that govern Bento are applied to PostShiba Privacy | Terms | Security