adiabatichottub

Also, High Forever track kind of bangs

It really depends on how paranoid you want to be. Removing their SSH keys and changing the root password will prevent casual snooping by rack-monkeys. If they need to change any hardware other than a drive they'll have to shut down the machine and you'll probably notice the gap in uptime. Keeping crucial data encrypted at rest will likely prevent pulling a mirrored drive and copying it. If that isn't enough security then you'll need to colocate and physically lock down the hardware yourself.

Text is wonderful, but note that the one keyword not found in this text is 'parse'. How much extra work is generated writing parers for text that would have been so much easier to deal with if it had just been generated in a structured binary format? You still get the pleasure of designing a new wheel with every format.

And then you add RFC2045 headers so you know what the encoding is...

I'll have to ponder the method you describe. I know I could implement that on my own mailboxes and some automated endpoints, but not sure how that would work for other users on our domain.

Indeed. Ultimately we're still relying on blacklists, Bayesian filters, and hueristics to detect actual SPAM.

I recently tried bouncing mail during the header phase when DMARC didn't align, but it rejected more legit emails than SPAM. Most of the junk we've been getting passes DMARC and has an unsubscribe link.

We just have to make it the cool thing to run your own mail server. B-)

The big changes I've seen over my lifetime have been tooling and materials. I remember when framers did everything with a hammer, a circular saw, and a speed-square. Now we have nail guns and cordless impact drivers and miter saws. Fiberglass batt insulation is still a thing, but now there's also urethane spray foam. We have engineered beams and OSB sheathing pre-coated with a moisture barrier. There's a lot of things that all add up to better performance and less manual labor.