When the Mail Stopped Coming Back

The first sign wasn't an error. It was the absence of one.

A client of mine — small accounting firm, four people, the kind of shop that lives and dies by attachments — called to ask why nobody was answering their invoices. Not bouncing. Answering. The invoices just weren't arriving, and the people they'd been sent to had no idea they'd been sent. No 550. No postmaster note. Nothing sitting in the deferred queue. The mail left my Postfix box clean, the logs said delivered, and somewhere past a Microsoft MX record it dropped into a hole that doesn't echo.

That's the part nobody warns you about when you decide to run your own mail. You expect failure to look like failure. The worst kind looks exactly like success.

I did everything the manuals said

This wasn't some misconfigured weekend project. I ran that stack the way you're supposed to. Postfix and Dovecot, hardened. SPF, DKIM and DMARC published and aligned. Forward and reverse DNS that matched, PTR pointing back at the hostname the server announced. TLS on submission, rspamd out front. I was enrolled in Microsoft's JMRP and watching Google Postmaster Tools. mail-tester handed me a clean 10/10. On paper I was indistinguishable from a real email provider.

None of it mattered, because the problem was never my config. The problem was the neighbourhood.

The box sat on a VPS, on an IP inside a /24 I didn't own and couldn't vet. One day someone four addresses down — compromised host, snowshoe spammer, take your pick — started spewing garbage. The range took a reputation hit, and Outlook started handing me back 550 5.7.1 ... part of their network is on our block list (S3150). Microsoft's own community guidance is refreshingly blunt about it: the block "isn't just on your specific IP address but on a larger network, likely your whole /24 subnet." I'd done nothing wrong and there was nothing I could do, because the thing being judged wasn't me. It was the company I'd been forced to keep.

You can fix your own mistakes. You cannot fix your neighbour's. That's the part that grinds you down.

The system is built to keep you out

Here's the structural fact the "just self-host it" crowd skips. Spamhaus runs a thing called the Policy Blocklist — end-user IP ranges that, by policy, "should never be sending email directly to the final destination." It covers north of 1.4 billion addresses, close to 40% of routable IPv4. Most residential space is on it. So is a lot of cloud and VPS space, by design. The assumption baked into the modern internet is that a machine like the one in your closet relays through an authenticated smarthost rather than talking to inboxes directly — and plenty of providers just block outbound port 25 to make sure of it.

So before your first message goes out, you're usually already presumed guilty. And the bar keeps climbing. Google's sender guidelines now read like a compliance audit — SPF or DKIM, a PTR that resolves back to your sending IP, TLS, complaints kept under 0.3% — and since the 2024 bulk-sender rules, high-volume senders who get authentication or alignment wrong get rejected outright instead of nudged. Late 2025 made it nastier still: Gmail began bouncing authentication failures at the handshake with 5.7.26, and Microsoft followed with 550 5.7.515 for senders missing proper SPF, DKIM and DMARC. Prove who you are or you don't reach any folder — spam included.

The honest one-liner came from Carlos Fenollosa, who self-hosted his own email for twenty-three years before throwing in the towel in 2022. His IP had sent zero spam for a decade. His alumni newsletters, his bank withdrawal alerts, his doctor's appointment reminders all quietly landed in spam anyway. His diagnosis is the one I keep coming back to:

At some point your IP range is bound to be banned [...] It's not if, it's when.

The fair version of the other side

I owe the other camp an honest hearing, because they aren't wrong about the facts.

Gilles Chehade, who wrote OpenSMTPD, has a well-known piece arguing that running your own mail is "not HARD but requires WORK" — two different things, and he's right. He means it as encouragement, too: he actively wants more people self-hosting, so the address space outside the big providers stays worth something. The software isn't mysterious. The protocols are old and boring and stable. Lots of people run small mail servers competently, and as a way to actually understand how email works end to end, I'd point anyone curious straight at it. Receiving mail on your own box is genuinely fine. Self-hosting is a wonderful teacher.

But notice where the pragmatic advice lands in 2026, even among people who love this stuff. Hand the outbound deliverability — the hard, rotting part, the IP reputation, the opaque mood of three megacorps — to someone who does it full time. Whether that's relaying through a smarthost or moving the mailboxes to a managed provider outright, it's the same concession: the part that gets worse every year is best not fought alone. We don't really disagree on the mechanics. We disagree on whether the fight is worth having.

For a hobbyist who enjoys the fight, it can be. For a four-person accounting firm whose invoices need to land, it never is. And the cost was never the monthly bill. It's the 2 a.m. tail of /var/log/maillog, the delisting forms with no self-service button, the security advisory you have to read before the scanners do — the day a critical Exim bug ships and you've got days, not weeks, before the bots find your unpatched box. That's not paranoia. That's the documented pattern, over and over.

What I tell people now

Don't self-host your business email. I get to say that the unglamorous way — by doing it, by being good at it, and by losing anyway to a system that was never going to let a one-person IP win.

Use Microsoft 365. The per-mailbox fee buys you out of the whole problem at once: a reputation Gmail and everyone else already trusts, spam filtering trained on a planet's worth of mail, an uptime SLA with money behind it, and the dull certainty that when something breaks at 2 a.m., it isn't your pager going off.

I'll be straight with you, because that's the entire point of a post like this: reselling Microsoft 365 is part of what Maxinodes does, so I'm not a neutral party. But the recommendation came first and the business followed, not the other way around. I started moving clients to managed mail because I was tired of explaining the S3150 bounce for the hundredth time. Selling it was just the honest next step.

I still self-host nearly everything else. This blog, my services, the metal under all of it. Email is the one box I handed back — and I sleep better for it.

Run your own server to learn how email works. Pay someone else to make sure it arrives.