Sending pauses itself at 3% bounces or 0.1% complaints.
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.
| Mailbox | Bounces (limit 3%) | Complaints (limit 0.1%) | Status |
|---|---|---|---|
| [email protected] | 0.8% | 0.0% | Sending |
| [email protected] | 1.1% | 0.0% | Sending |
| [email protected] | 3.4% | 0.0% | Paused |
| [email protected] | 0.6% | 0.0% | Sending |
- 1We pause a mailbox that crosses a limit, and tell you why.
- 2We measure bounces and complaints against the limits.
- 3We verify addresses before they are ever emailed.
What you get
Every address verified
Every address is verified before sending, and addresses on catch-all domains get a second check.
Sending stops 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
Verified before sending
Fake, mistyped and throwaway addresses are removed. Addresses on catch-all domains get a second opinion.
Every send is watched
Bounce rate over the last 7 days (once a mailbox has 100 sends) and spam complaints are checked constantly.
It pauses automatically
If a limit is crossed, sending stops at once. Nothing waits for you to click.
You are told what happened
You see which mailbox tripped, what the number was and what happens next.
What runs on its own, and what you decide
Runs on its own
- 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 decide
- 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.
A bad batch on a Thursday
Example. Names are invented.
- 6:00 amA new area is added. Verification removes 23 of 412 addresses before anything sends.
- 6:12 amOne mailbox still crosses 3% bounces. It pauses on its own.
- 6:13 amThe other 19 mailboxes keep sending. Sam gets a plain note explaining what happened.
- FridayThe paused mailbox goes back through warm-up before it sends again.
Doing it yourself vs Pipefire
| Doing it yourself | PipefireAutomatic |
|---|---|
| Run your list through a separate verifier | Every address verified for you |
| Notice the bounce rate a week too late | Bounces and complaints watched on every send |
| Remember to pause the campaign yourself | Pauses on its own at 3% bounces or 0.1% complaints |
| Start again with new domains | One 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 and what happened next. The mailbox is recovered or replaced at no extra cost.
Also in Pipefire: Cold email infrastructure · Your agent team · Domains and mailboxes · Warm-up · Prospect finding · Contact forms · Email writing · A/B testing · Reply inbox · 24/7 monitoring
A bad week costs you one mailbox, not your whole setup.
Separate domains, warmed and watched for you, so the domain your clients email stays clean.