This month’s headline in deliverability news came from a stage in Cupertino and an unexpected document drop at the IETF. Different worlds, same pressure: more is being asked of senders with every passing month, and June was no exception.
Apple held WWDC on June 9 and poured more AI into Mail. Around the same window, the spec that dictates email authentication for the entire internet became an official standard for the first time in over a decade. One of those changes is front and center. The other will most probably kill a campaign six months from now while nobody connects the dots.
There’s also a reason to finally care about reaching DMARC enforcement this year, and it has nothing to do with avoiding the spam folder. More on that in the rest of this article.
Key takeaways
- Apple accounts for 51.52% of all email opens (Litmus, February 2026). Its on-device categories decide which of four buckets you land in before a human looks.
- Time-sensitive content is a documented path into Primary, regardless of which category you normally land in.
- DMARC is now RFC 9989. The pct tag, the only in-protocol tool for easing into enforcement, is gone.
- Apple Branded Mail and BIMI both require DMARC at enforcement. p=none does not qualify for either.
Apple just made its inbox smarter, and you weren’t invited
Apple isn’t a sliver of your list. Litmus, measuring more than 1.1 billion opens in February 2026, puts Apple at 51.52% of the global email client market, with Gmail next at 26.72%. Together, they account for nearly 90% of all opens.
What WWDC confirmed is that Apple is not finished building inside that environment. The keynote on June 9 introduced smarter AI-generated reply suggestions in Mail and deeper cross-app context awareness, with Apple Intelligence now reading across messages to suggest actions before users ask. The categories themselves (Primary, Transactions, Updates, and Promotions) have been the default since iOS 18.2. What is changing is the sophistication of what routes mail into each one.
The categorization runs on-device, so there is no single server-side algorithm to reverse-engineer because each inbox runs its own local model, trained on how that specific user has behaved with your mail over time. Game one inbox and you have gamed exactly one inbox.
There is, however, a documented lever. When a message in Transactions, Updates, or Promotions carries time-sensitive information, Apple places it in Primary as well. A shipping update with a precise delivery window earns that second placement. So does a reminder about tomorrow’s appointment. The mechanism is clearly stated in Apple’s own documentation, and it rewards mail that comes with genuine urgency, which is an important point to remember.
DMARC just became an official standard. One thing disappeared with the old version.
In May 2026, the IETF published RFC 9989 alongside RFC 9990 and RFC 9991, covering the DMARC protocol, aggregate reporting, and failure reporting, respectively. The work was led by Todd Herr and John Levine. For eleven years, DMARC operated under an informational RFC, meaning it had no formal standards implications. That changed with this publication. DMARC is now on the Standards Track.
For most senders, the practical implications have barely changed. Existing records keep working, and the version string stays v=DMARC1. No emergency changes are required.
One thing did not survive the update: the pct tag.
That tag lets domain owners apply their DMARC policy to a percentage of failing mail rather than all of it. Set p=reject with pct=10, and only a tenth of non-compliant messages actually got rejected. It was the mechanism cautious senders used to test enforcement without committing to it fully. As EasyDMARC noted in its May analysis, the tag was ambiguously defined from the start. Different receivers interpreted it differently, and in practice, almost nobody configured it correctly.
The new RFC 9989 spec introduces a binary testing flag as a replacement, but there is no direct equivalent for the gradual percentage rollout pct enabled. The crossing from monitoring to enforcement, always the most fraught step in DMARC, now happens without a dimmer switch. You are watching, or you are enforcing.
Enforcement is now the price of admission for your logo
Apple Branded Mail and BIMI (the features that display your brand logo next to your sender name in the inbox) both depend on the same DMARC requirement: a policy of p=quarantine or p=reject. Monitoring at p=none does not qualify for either.
This is a concrete reason for anyone who’s been parked at p=none and looking for a reason to move. Apple’s path is relatively low friction. Branded Mail runs through Apple Business Connect: verify your domain, confirm DMARC is at enforcement, and the logo becomes eligible to appear. A Verified Mark Certificate is not required, unlike the classic BIMI route. That is a meaningful return on an authentication task for a sender whose audience skews heavily toward Apple devices, which describes most consumer-facing programs given Apple’s market share.
BIMI covers the Gmail and Yahoo side of the equation. It comes with more requirements, including a hosted SVG logo file and, in some configurations, a certificate.
Two providers. Same entry fee.
What to watch for next
Two things. Whether Microsoft Outlook ever joins the logo ecosystem remains an open question. It currently supports neither BIMI nor Branded Mail, which leaves a gap for programs with heavy enterprise audiences. Given that Microsoft has already enforced SPF, DKIM, and DMARC for bulk senders since May 2025, the authentication groundwork is there. We’re only waiting for the display part of it.
And while Apple’s inbox is becoming harder to game and easier to lose ground in, there’s still a lot you can do. With InboxAlly, you can build the right kind of engagement that those systems respond to, so your emails have a better shot at staying visible as AI sorting gets more strict. Book a demo and see how your inbox placement changes under the right sending conditions.