valimail
Reporting is an important part of DMARC. It provides valuable feedback from mailbox providers to help you identify any problems with authentication of your legitimate emails, and allows you to monitor for fraudulent email misuse of your domain name. But lots of people set up DMARC without understanding the reporting component — I myself have been guilty of simply routing DMARC reports (which tend to comprise a low volume if emails containing XML-formatted data attachments) to a folder or mailbox to review them “someday.” And if that day ever comes, I figure it would be good to understand what I’m looking at as far as the two different types of DMARC reporting — and why, ultimately, RUA (aggregate) reporting is all I (and you) should rely on. When creating a “reporting address” for your DMARC record, you might notice that there are two different “reporting” fields in the DMARC record
Looking for guidance on how to create your BIMI logo file? Valimail has a pretty good guide that explains the requirements and they also explain what to keep in mind when creating your BIMI graphic SVG file. Starting with:SquareSVG Tiny Portable/Secure formatSolid backgroundPublished via HTTPSSVG meaning a Scalable Vector Graphics file, and particular type of SVG called SVG Tiny Portable/Secure (SVG P/S). The image has to truly be a vector graphic; the overall SVG spec does allow you to embed a bitmap in a file but this isn’t allowed for SVG P/S or BIMI usage.The Valimail guide goes on to explain how to manually edit the SVG file to convert it to the SVG P/S spec. But if you don’t feel like editing XML files by hand, download this converter application that the BIMI (AuthIndicators) Working Group has shared here. I’ve used the Macintosh version and it works fine. (You…