- October 2021
- Engineering Memo · External Release
Poor bounce handling has a cost that is specific, measurable, and often larger than it appears before an incident occurs. This note quantifies the cost across three dimensions: deliverability reputation, sending capacity, and operational response time.
A hard bounce — a 5XX permanent SMTP failure — indicates that an email address is permanently invalid. The ISP's mail server is telling you definitively: this address does not exist, do not send to it again. If the sending system ignores this signal and retries the address in subsequent campaigns, the ISP sees the repeated send to a non-existent address. This is one of the clearest signals of a poorly managed sender, associated with scraped lists and spam operations. The repeated send creates a negative permanent mark in the ISP's reputation model for the sending IP and domain.
The Reputation Math
Gmail Postmaster Tools measures sender reputation partly on the signal-to-noise ratio of outbound traffic. Messages to invalid addresses are pure noise — they contribute nothing to positive engagement signals and actively contribute to negative ones. A sender with 5% hard bounce rate is sending 1 in 20 messages to addresses the ISP knows are invalid. At scale (1 million sends per campaign), that is 50,000 invalid-address sends per campaign — 50,000 negative data points accumulating in the ISP's model, per campaign, on every send.
The industry threshold at which bounce rate begins affecting reputation at most ISPs is 2% for bulk senders. Above that threshold, inbox placement starts declining. The decline is not immediate — reputation systems average signals over time — but it is consistent. Senders who operate with high bounce rates for extended periods find that deliverability recovery takes 6-8 weeks of clean sending even after the bounce rate is fixed, because the historical negative signals are slow to decay.
Sending Capacity Cost
Every message sent to an invalid address consumes sending capacity — bandwidth, SMTP connections, queue processing, and hourly volume budget at the ISP. A sender with a 5% hard bounce rate is using 5% of their sending capacity on messages that will never deliver and that actively harm their reputation. At 500,000 sends per month, this is 25,000 messages per month of wasted capacity, plus the reputational drag on the remaining 475,000.
The Operational Response Requirement
Correct bounce handling requires global suppression — an address that bounced on campaign A must be suppressed from campaigns B, C, and D without manual intervention. The suppression must be automatic, immediate, and persistent. In PowerMTA + MailWizz configurations, this requires bounce server integration, accounting log processing, and global blacklist management to work correctly. Any gap in this chain — delayed bounce processing, incomplete suppression propagation, or a list import that overwrites existing suppressions — recreates the problem.
Our managed infrastructure configures and monitors the full bounce processing pipeline as part of standard setup. Infrastructure assessment →