Skip to content
Invitation-only alpha. Features and limits may change as we learn from testing.

Bounces and suppressed addresses

  • Immediate: the recipient’s server refuses the message during delivery. The result appears in the message history straight away.
  • Later (a bounce): the server accepts the message, then sends a delivery failure report minutes or hours later. weneed.email receives that report and links it to your message.

When a failure is permanent (for example, the mailbox doesn’t exist), the address is suppressed. New messages to it are still accepted and recorded, but not sent. The history shows them as suppressed.

This protects your sending reputation. Repeatedly sending to dead addresses is one of the fastest ways to get blocked by large mailbox providers.

In Control, open Blocked recipients in your project and enter one exact address. The page shows whether it is blocked, the reason (a permanent bounce, a spam complaint, or a block by weneed.email), since when, and the message that caused it when that message belongs to this project. It also shows how many addresses your workspace blocks in total. There is no list or export, for privacy.

With a read key that has suppressions:read, the API answers the same question: GET /v1/suppressions?address=. See the API reference.

Blocks apply to every project in your workspace. Older blocks may show no start date; that date was not recorded at the time.

  • Treat a suppressed address as invalid in your own app: ask the user to confirm or change it.
  • Don’t create a new account or credential to get around suppression.
  • Keep bounces low. Too many permanent bounces pause sending; see If sending is paused.

Removing a block is a request that support reviews. Write to support with the address and why you believe it can receive mail again, for example because the user confirmed a fixed mailbox. Sending again before the cause is fixed can pause your sending.