It's finally here! Well, full, public Gmail support for BIMI is finally here. On Monday, July 12th, Google announced that they are in the process of rolling out "general support" for BIMI in Gmail. Read Google's announcement here.
At the same time, the AuthIndicators Working Group -- developers of the BIMI standard -- put out a press release talking up the new general support of BIMI at Gmail, and explained that this means that "BIMI [will] be available to Gmail, Yahoo, and Fastmail inboxes." Read that here.
As Gmail's BIMI support requires a "verified mark" certificate (and by extension, trademark verified logos), that may leave you wondering where to start, if you're looking for the right partnership to help guide you through the implementation of all of this. Entrust and Red Sift have got you covered -- this press release explains how their partnership can provide you "a streamlined onramp to BIMI." Read that here.
July 13 Update: Yesterday, Mailkit rolled out notamiq.com, a new platform that helps senders streamline BIMI deployment. They say: "No need to worry about hosting the SVG and VMC files or having to get in touch with their IT when DNS updates are needed. Just delegate their BIMI DNS record and easily manage settings directly in the Notamiq user interface." They plan to add VMC registration directly into the UI as soon as Entrust and Digicert have their APIs ready and tested. That should allow users not only to easily deploy BIMI but also get hassle-free VMC registration, VMC deployment as well as renewals. Learn more about it here.
If you've got information on other vendors offering something similar, please let me know and I'll add their info here.
One thing that's still missing here is BIMI support from Microsoft. They're still rather a large mailbox provider and that leaves a significant gap in the BIMI ecosystem. Will Microsoft come around to support the BIMI standard? I haven't heard a peep on this front in years, and Microsoft's similar mechanism ("brand cards") seems to be abandoned. Time will tell, I guess.
(Thanks to Andrew Mann for the tip on these developments!)