In the past year, we've seen a growing interest in everything related to the security and safety of emailing.

Mostly, big emails providers like Yahoo and GMail asking their senders to comply with the DMARC RFCs.

As one of the first employees of Mailjet, it rang a bell. We used to manage IP pools, ban bad players from our service, communicate a lot with senders to improve the overall quality of emails. And I loved it! My role at Mailjet was to bootstrap the Developer Relations team. The exact team that would reach out to our customers and help them integrate with our APIs, yes, but that would also provide them guidance and training on how to setup their whole sending environment. Because as an ESP there is so much of the authorization work that you can just check, but not control. An optimal DNS configuration, the content of the emails... lots of moving parts on the customer's end.

Even if I am now working on digital health, we just cannot do business when our communications do not reach our user's mailboxes. Imagine a magic link system where the emails do not reach the inbox? Users cannot connect at all and that's a disaster. So even apps depends on emails.

Lastly, the French government is also promoting DMARC as one new step, with a recently published guide to DMARC configuration. So, seeing all these incentives for DMARC and DNS authorization and building with a team of friends in Paris and in Houston, after managing our own reporting emails and processing XML with our own eyes for a few years... have built DMARCTrust, a new SaaS tool for DMARC maintenance.

The platform already allow anyone to check their current DMARC configuration from their records, but also check or generate new records (including BIMI). In the near future, we will also offert expert services to help users monitor feedback and quickly identify what's wrong in their configuration.

We are confident on the fact that one needs great tools to handle all these technical aspects of deliverability.