Why is the wrong BIMI logo displaying in Yahoo and AOL and how can I fix it?
Summary
What email marketers say9Marketer opinions
Email marketer from Reddit suggests that the BIMI logo issue may stem from not fully meeting Yahoo/AOL's requirements for sender reputation or authentication. They propose checking sender score, ensuring consistent email volume, and verifying that SPF, DKIM, and DMARC records are correctly implemented and passing authentication checks.
Email marketer from EmailVendorSelection Blog shares that a frequent issue is the SVG logo not being properly optimized, leading to rendering problems. They recommend using an SVG optimizer tool to reduce file size and complexity while maintaining visual quality.
Email marketer from an email marketing forum suggests making sure that the URL provided in the BIMI record for the SVG image is directly accessible over HTTPS and doesn't require any authentication or redirects. A broken or inaccessible link will prevent the logo from displaying.
Email marketer from mailhardener.com shares that using a subdomain for email sending, and setting up BIMI on that subdomain might cause problems, as mailbox providers look at the root domain for BIMI records. BIMI record should be set up for the root domain to fix logo display issues.
Email marketer from Mailjet Blog explains that incorrect BIMI logo display might be due to caching issues at the mailbox provider level, suggesting that it can take time for changes to propagate across systems. They recommend ensuring the SVG file is correctly formatted, publicly accessible, and that the DNS records are properly configured. Contacting the mailbox provider directly is also advised if the issue persists.
Marketer from Email Geeks shares that sometimes Yahoo/AOL needs to 'kick the box' to ensure everything is updated and that it might take a week or so for changes to reflect, advising to set client expectations accordingly.
Email marketer from GMass explains that a Verified Mark Certificate (VMC) is typically needed, and it needs to be from an authorized provider.
Email marketer from Litmus suggests using BIMI testing tools and BIMI record generators to check for errors. This ensures the validity of the record before submitting it.
Email marketer from SparkPost Blog emphasizes that a DMARC policy of 'p=quarantine' or 'p=reject' is essential for BIMI to function. They recommend carefully reviewing DMARC reports to identify and address any authentication failures that could prevent the logo from displaying.
What the experts say2Expert opinions
Expert from Email Geeks explains that if an image is already showing, it means Yahoo/AOL already trusts the traffic and is displaying a logo on file. If all BIMI criteria are met, the correct logo will be pulled automatically, but this takes time. If the correct logo doesn't appear after a while, the user should reach out to the provided email address.
Expert from Spam Resource explains that sometimes the wrong BIMI logo appears due to caching at the mailbox provider level. He advises that after making changes, it can take time (days or even a week) for Yahoo and AOL to update their cache and display the correct logo. He suggests patience and periodic re-checking.
What the documentation says3Technical articles
Documentation from Yahoo Sender Hub suggests ensuring the VMC is valid and issued by an approved certification authority, as well as making sure that the BIMI DNS record is published correctly with the right selector and SVG URL. It notes that Yahoo may cache logos and advises waiting up to 72 hours for changes to propagate.
Documentation from Cloudflare explains that BIMI records must be correctly formatted and placed in the DNS settings. It needs the correct syntax, including the selector and the URL of the SVG image. Any errors in the record can prevent the BIMI logo from displaying.
Documentation from BIMI Group explains that the SVG file must adhere to specific formatting guidelines, including being a vector graphic, not exceeding a certain file size, and containing no external links or scripts. It also needs to be accessible over HTTPS.