$ whoami
the mailprotector engineering blog
Field notes from the people building email security at Mailprotector. How we get the good mail through, stop the bad, and keep a few decades of SMTP running, including the long nights that come with it.
// new posts, in your inbox
How Shield Blueprints lets MSPs set customer defaults and update existing settings without repeating the work for every organization.
Ben Hathaway
Chief Technology Officer
Why people treat the junk folder as a second inbox, and how that behavior changed the way we designed Shield's Security Briefing.
Ben Hathaway
Chief Technology Officer
Why Shield uses Zero Trust to control inbox access and a language model to summarize mail. The product design choices behind intentional AI.
Ben Hathaway
Chief Technology Officer
Coding skills are important, but understanding the business logic and industry behind the software may matter even more as AI coding tools improve.
Andy Barringer
Director of Software Development
AI made it cheap to generate a phishing message for one person, use it once, and adapt every follow-up to the target's replies. Here is what that changes for email detection.
Ben Hathaway
Chief Technology Officer
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.
Ben Hathaway
Chief Technology Officer
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.
Ben Hathaway
Chief Technology Officer
