$ ls archive/2026/
6 posts in 2026.
Email is a federated protocol with decades of implementations behind it and an adversary working the gaps on purpose, so the set of things your product has to handle is discovered rather than designed. How we run QA at Mailprotector without a QA department.
The engineering story behind Shield's Deployment Control release: how deployment and rollout became separate steps, how health checks gate enablement, and the routing redesign that removed DNS from the process.
Three versions of Shield's mail flow architecture, from a blunt MX record to a design that hands the last mile back to Microsoft, and what changed each time along the way.
Phishing simulations produce compliance artifacts, and that's why they persist even though they don't protect users. The technical case for moving the trust decision off the content an attacker controls.
A new mail-flow rollout made Microsoft 365 attribute every customer's mail to our tenant. The undocumented rule behind it, and the fix.
Why an email security company is starting an engineering blog, and what we plan to put here.
