Industry Updates
A running record of the changes that move the inbox: mailbox-provider policy shifts, new authentication standards, privacy and legal rules, blacklist and reputation news, and the acquisitions reshaping the space. Each entry is dated, rated for impact, and written to answer one question - what changed, and what should you do about it.
Gmail will stop letting you send mail as a non-Google address (@yahoo.com, @outlook.com or a custom domain) from the web and mobile apps, and will retire Gmailify and web POP fetch for third-party accounts. Existing users keep the features until January 2027; new sign-ups already lost Gmailify and POP after Q1 2026.
EffectiveJanuary 2027
A new IETF draft (draft-brotman-aggregate-performance-reporting) proposes a DMARC-style mechanism for mailbox providers to email senders daily JSON reports on inbox placement and engagement - keyed to the DKIM signing domain, not the From address. It is early (Comcast is the only provider sending beta reports, with a Google engineer among the authors), but it could finally standardize the placement data that has always lived behind per-provider portals.
A revived IETF working group is rebuilding DKIM from the ground up. DKIM2 (draft-ietf-dkim-dkim2-spec, authored by engineers from Yahoo, Google and Fastmail) signs every hop, binds each signature to the SMTP envelope to stop replay, records reversible "recipes" so forwarding no longer breaks DMARC, and routes provable bounces up the chain - and a companion draft retires ARC into it. It is real enough to watch (working code exists), but still a draft: do not deploy it in production yet.