Illingworth says a client went 68 days without inbox checks

Richard Illingworth says an outbound org he looks after has gone 68 days without logging in once to check on their inboxes. Back in August, he says, someone there was pulling sick inboxes out of sending by hand, 23 of them at one point.

The change he describes is dated. All of that org's inboxes went on his monitoring portal on 12 August. Since then the portal checks every inbox every hour, and Illingworth says they have stayed connected 99.952% of the time. Dead addresses get blocked every morning, 12,817 of them so far.

Richard Illingworth

@RCIllingworth

X

dead addresses get blocked every morning, 12,817 so far

What the automation is doing

The mechanic is simple enough to copy without buying anything. An inbox that starts bouncing or failing warm-up is pulled out of the sending rotation automatically, then put back into rotation the day it is healthy again. That is the same job the person in August was doing by hand, 23 inboxes deep, just run hourly instead of whenever someone remembered to look.

Illingworth's framing is that the org "got on with the selling" while the inbox babysitting moved off their plate. He ends the post with a link in bio for inboxes and support, which is the tell on how to read the figures.

For people sending

These are a vendor's numbers for its own service, so the 99.952% uptime is a product claim, not an independent benchmark. There is no reply rate, no volume and no revenue figure attached to the 68 days, only a connection statistic and a count of blocked addresses. A client who has stopped logging in is not evidence that results held, it is evidence that nobody is checking.

The underlying problem is real and Illingworth has posted on it before. He earlier published an audit where roughly half of one agency's 10 million emails came out of inboxes that should have been pulled from sending. If a sick inbox keeps sending because nobody noticed, the damage compounds across the whole sending pool, which is the argument for hourly checks whoever runs them.

The number worth stealing here is the one nobody prices. If a human was manually removing 23 inboxes at a time in August, that is a recurring task with a frequency and a failure mode, and the failure mode is sending from an inbox that is already bouncing. Whether you buy a portal or write a cron job, the rule Illingworth describes is the thing to implement. Out on bounce or failed warm-up, back in when healthy, dead addresses stripped daily.