BIMI

BIMI only works on top of strict DMARC: p=quarantine or p=reject, a published sp= must not be none, no pct below 100 — and no t=y. On t=y the published sources are silent: RFC 9989 §4.7 says receivers apply the policy one level weaker under test mode, but the BIMI draft speaks only of the published p. We treat a record in test mode as not enforcing, because a logo that never appears has already cost a VMC — remove t=y before you buy one. On the pct point the sources differ too — the BIMI draft asks for pct=100 only under p=quarantine, the BIMI Group’s guide asks for it in every case — and this site follows the stricter one. Removing the tag is the fix, but align your sending paths first: conforming receivers already ignore pct, receivers still on RFC 7489 do not, and deleting it lifts them to full enforcement. The logo must be an SVG in the Tiny Portable/Secure profile and served over HTTPS. That profile asks for the file to be as small as possible and to stay under 32 KB measured uncompressed — draft-svg-tiny-ps-abrotman §2.4 states this as a SHOULD, not a hard limit, and our own check does not reject a larger file; the sender test reports it as larger than recommended. Gmail and Apple Mail additionally require a Verified or Common Mark Certificate (VMC/CMC) referenced via a=. The optional avp= tag (avatar preference) tells providers which indicator to prefer when the sender ALSO has a personal avatar — and only at providers that support both. The default avp=brand asks for the brand logo; avp=personal asks for the sender’s personal avatar, with the brand logo shown when that sender has none (BIMI draft §4.3, a SHOULD). Leaving the tag out is the same as avp=brand. Note that BIMI is an Internet-Draft, not an RFC – details may still change.