A growing need for DMARC?
Yahoo and Gmail now require DMARC compliance. Senders who ignored it for years are scrambling.
I’ve been here before. At Mailjet, I bootstrapped the Developer Relations team, then the London and Berlin offices. Met hundreds of developers, dozens of startups. We managed IP pools, banned bad actors, and spent hours helping customers fix their DNS. The frustrating part: as an ESP, you can check configurations but you can’t control them. Customers own their DNS, their content, their sending reputation.
Even now, working in digital health, email deliverability matters. Imagine a magic link auth system where emails don’t reach inboxes. Users can’t log in. Everything breaks.
The French government recently published a guide to DMARC configuration. More pressure on organizations to get this right.
After years of parsing DMARC XML reports manually, I built DMARCTrust. Solo. No VC, no roadmap dictated by investors. Just a tool I needed, now available to others. Check your config, generate records (including BIMI), monitor feedback. Scratching my own itch.