Why is the wrong BIMI logo displaying in Yahoo and AOL and how can I fix it?

Key findings

• Yahoo's logo selection: If a BIMI logo isn't displayed as expected, Yahoo may resort to an internal proprietary solution to display a logo already on file, indicating they trust your traffic but haven't fully processed or recognized your BIMI record.
• VMC not always required: While a Verified Mark Certificate (VMC) is required by some mailbox providers like Google, Yahoo and AOL may still display a self-asserted BIMI logo if all other criteria are met, though a VMC can enhance trust and ensure consistent display.
• Propagation and caching: DNS changes for BIMI records can take time to propagate across the internet and for mailbox providers to refresh their cache. Delays of several days, or even a week, are not uncommon before the correct logo appears.
• Direct contact with Yahoo: For persistent issues where the wrong logo is displayed despite correct setup and sufficient waiting time, contacting the Yahoo BIMI team directly is often recommended. They can sometimes kick the box and expedite the update.

Key considerations

• Verify SVG format: Ensure your SVG logo adheres strictly to the SVG Tiny Portable Secure (SVG Tiny 1.2) profile. Incorrect SVG formatting is a frequent cause of BIMI display failures. You can find more information on how to validate your BIMI SVG for proper configuration.
• DNS record accuracy: Double-check your BIMI DNS TXT record for any syntax errors or misspellings. Even a small error can prevent the record from being parsed correctly. Resources like this guide to BIMI can help with proper setup.
• DMARC enforcement: BIMI requires a DMARC policy set to at least p=quarantine or p=reject. If your DMARC policy is p=none, your BIMI logo will not display. Learn more about DMARC implementation.
• Patience is key: Allow sufficient time for all systems to update. Even after direct contact with support, changes may not be instantaneous.

Key opinions

• Unpredictable display: Many marketers report that even with correct BIMI setup and DNS records pointing to the right SVG, Yahoo and AOL may display an unexpected or random logo, suggesting an internal logic at play.
• Caching delays: A common observation is that updates to BIMI logos can take a significant amount of time, sometimes a week or more, to propagate and refresh within the mailbox providers' systems.
• Need for direct intervention: Marketers find that reaching out to the Yahoo BIMI team directly can be an effective way to prompt an update when standard troubleshooting doesn't yield results.
• Managing client expectations: Due to potential delays and the need for external intervention, marketers emphasize the importance of setting realistic expectations with clients about the timeline for BIMI logo display.

Key considerations

• Persistent monitoring: Even after initial setup, continuous monitoring of BIMI logo display across various email clients, including Yahoo and AOL, is crucial to catch and address unexpected changes or issues. Tools that offer DMARC monitoring can assist with this.
• Comprehensive checks: Before contacting support, ensure that all aspects of your BIMI setup, including your DMARC record and SVG file, have been thoroughly validated using multiple tools. Consider our email deliverability tester.
• External validation tools: Utilize third-party BIMI validation tools to confirm your record's health and SVG accessibility. While these tools don't guarantee display, they can flag obvious errors. For example, Mailgun's blog mentions the DNS TXT record for BIMI.
• Documentation for reference: Keep Yahoo's official BIMI documentation handy as a primary reference for their specific requirements and troubleshooting guidelines.

Key opinions

• Trust and existing logos: If Yahoo is displaying any image, it indicates a level of trust in the sender's traffic. They may be pulling an older or proprietary logo from their files before the new BIMI logo is fully recognized and pulled.
• Time for automatic pull: Experts confirm that if a BIMI logo meets all criteria, it will eventually be pulled automatically, but this process takes some time to update across systems.
• Official support channel: The recommended course of action for persistent incorrect logo display is to reach out to the mailbox provider's dedicated BIMI support team, who can investigate and potentially expedite the change.
• Content for common issues: Experts acknowledge the frequent occurrence of wrong BIMI showing issues and see value in creating public resources to guide senders.

Key considerations

• Utilize official resources: Always refer to the mailbox provider's official sender guidelines and BIMI pages for the most accurate and up-to-date information. For Yahoo, this includes their specific senders portal.
• Patience before escalation: Allow a reasonable timeframe (several days to a week) for changes to propagate before escalating the issue to support, as immediate results are atypical. This is also covered in our guide on Yahoo cache updates.
• Avoid generic support channels: When contacting support, ensure you are using the specific email address or channel designated for BIMI or sender-related issues to get to the correct team quickly. You can read more in our troubleshooting guide for Yahoo.
• Prepare detailed information: When contacting support, provide comprehensive details including your domain, BIMI record, SVG URL, and any specific emails where the incorrect logo is observed. This helps the support team diagnose the issue efficiently.

Key findings

• SVG format specifics: Documentation consistently stresses that BIMI logos must be in SVG Tiny Portable Secure (SVG Tiny 1.2) format and often square dimensions. Incorrect SVG formatting is a common reason for display issues, or for a default logo being pulled instead.
• DNS record syntax: The BIMI record is a DNS TXT record. Documentation provides precise syntax rules for this record, and any deviation can prevent mailbox providers from correctly identifying and utilizing it.
• DMARC enforcement policy: BIMI relies on strong email authentication. Documentation confirms that a domain must have a DMARC policy set to p=quarantine or p=reject for BIMI to be considered.
• Mailbox provider discretion: Even with correct setup, documentation notes that only mailbox providers that support BIMI will display the logo, and some may have internal processes or trust signals that influence logo selection, especially if a Verified Mark Certificate is absent.

Key considerations

• Strict SVG compliance: Pay close attention to all SVG requirements. Even minor deviations in code can lead to display failures on certain platforms. For more details, consult the guide on BIMI logo size recommendations.
• DNS record validation: After publishing your BIMI DNS record, use a reputable online validation tool to confirm its accuracy and accessibility. This is a critical step in implementing BIMI correctly.
• DMARC alignment checks: Regularly monitor your DMARC reports to ensure proper SPF and DKIM alignment, as BIMI depends on a healthy DMARC enforcement policy. Read more about DMARC reports from Google and Yahoo.
• Understand VMC requirements: While not universally required for Yahoo/AOL, note that Google and other providers may require a Verified Mark Certificate (VMC). If you plan for broader adoption, this is a future consideration.