Menu
Bounce and spam protection

We pause your sending as soon as bounces or spam complaints rise.

One bad list can ruin a domain in a day. Pipefire checks every address before it is emailed and watches every send. If bounces pass 3% or spam complaints pass 0.1%, sending stops by itself and you are told why. A bad week costs you one mailbox, not your whole setup.

  1. 1We pause a mailbox that crosses a limit, and tell you why.
  2. 2We measure bounces and complaints against the limits.
  3. 3We verify addresses before they are ever emailed.
Example screen with invented numbers: bounce and complaint rates per mailbox, and a pause that happened on its own.

What you get

We verify every address

Every address is verified before sending, and addresses on catch-all domains get a second check.

We stop sending before it does damage

The pause triggers at 3% bounces and 0.1% complaints, the levels mailbox providers act on.

The rest keeps sending

Only the mailbox that tripped comes out of rotation. Your other mailboxes carry on.

How it works

01

We verify before sending

Fake, mistyped and throwaway addresses are removed. Addresses on catch-all domains get a second opinion.

02

We watch every send

Bounce rate over the last 7 days (once a mailbox has 20 sends) and spam complaints are checked constantly.

03

We pause it automatically

If a limit is crossed, sending stops at once. Nothing waits for you to click.

04

We tell you what happened

You see which mailbox tripped, what the number was and what happens next.

What runs on its own, and what you decide

Pipefire does this for you

  • Verifying every address before it is emailed
  • Measuring bounces and complaints on every send
  • Pausing a mailbox or campaign that crosses a limit
  • Honoring every unsubscribe

You stay in charge of

  • Pausing or resuming a campaign at any time
  • How to recover a paused mailbox on Standard
  • Which areas and businesses you target

When something goes wrong

Bounces climb past 3%

Sending stops for that mailbox at once. You see the rate, the window and what happens next.

A prospect marks you as spam

Complaints are counted against the 0.1% limit and the address is never emailed again.

A whole area turns out to be a bad list

Addresses that fail verification are dropped before sending, so the damage never reaches your mailboxes.

An example, with an invented business

A bad batch on a Thursday

  1. 06:00A new area is added. Verification removes 23 of 412 addresses before anything sends.
  2. 06:12One mailbox still crosses 3% bounces. It pauses on its own.
  3. 06:13The other 19 mailboxes keep sending. Sam gets a plain note explaining what happened.
  4. FridayThe paused mailbox goes back through warm-up before it sends again.

Doing it yourself vs Pipefire

Doing it yourselfPipefire⚡ Done for you
Run your list through a separate verifierEvery address verified for you
Notice the bounce rate a week too lateBounces and complaints watched on every send
Remember to pause the campaign yourselfPauses on its own at 3% bounces or 0.1% complaints
Start again with new domainsOne mailbox comes out, the rest keep sending

Questions

What bounce rate is too high for cold email?

Mailbox providers start to distrust a sender at a few percent of hard bounces. Pipefire pauses at 3%, before that becomes lasting damage.

Do you email info@ and other shared inboxes?

Yes. For small businesses the shared inbox is often the one the owner reads, so Pipefire sends to them, and writes to the business rather than to "Hi Info".

What happens after a pause?

You see what tripped. On Standard you choose how to recover the mailbox; on Pro and Scale a replacement is set up automatically.

Your real domain never touches cold email.

Separate domains, warmed and watched for you, so the domain your clients email stays clean.