Google announced that it will retire Gmailify and stop fetching mail from other accounts via POP starting in January 2026. Gmailify let users link a non‑Google mailbox (Yahoo, Outlook or others) to Gmail so the messages benefited from Google’s spam filtering, labels and malware scanning. In the same update, Google said the “Check mail from other accounts” option – which uses POP3 to pull in third‑party mail – will also be removed from the Gmail web interface. Users can still access Gmail from a third‑party client via POP or IMAP and can still import messages via a one‑time migration; the discontinuation applies to Gmail acting as a POP client for other inboxes. Google’s support article doesn’t specify the exact day in January when the feature disappears, so it is safer to say the retirement begins “in January 2026.”
The deprecation coincides with Google’s tightening enforcement of its bulk‑sender guidelines. Since February 2024 Google has required high‑volume senders (5,000+ emails per day) to authenticate email and honor one‑click unsubscribe links. In an October 2025 FAQ update Google said it will ramp up enforcement in November 2025, warning that non‑compliant traffic may be delayed or rejected. These developments underscore a broader industry shift toward mandatory authentication and alignment.
Why Gmailify Mattered
Gmailify was more than a convenience feature. By ingesting external mail via POP and normalising it inside Gmail, Google effectively acted as an implicit trust broker for messages that might otherwise have failed modern authentication checks. A 2025 blog post by the hosting provider Mythic Beasts explains that Gmail’s “Check mail from other accounts” function pulled messages into Gmail as if they had been forwarded, but “with one crucial difference – it works reliably”.
The feature became a workaround because “efforts to make it harder to spoof email have also made it much harder to forward email reliably”, and until now Mythic Beasts recommended using Gmail’s POP‑fetch as an alternative to forwarding. The underlying problem is that forwarding often breaks SPF and DMARC alignment. When a message is forwarded, the receiving server sees the forwarder’s IP rather than the original sender’s IP; if the domain’s SPF record is strict, the message fails authentication and may be rejected. Gmail’s POP aggregator sidestepped that problem by collecting the mail directly and then applying its own spam filtering – effectively laundering the message’s reputation. As Mythic Beasts notes, after the retirement users must rely on forwarding (which carries a risk of rejection) or switch to a dedicated email client.
Interpretation of the Technical Implications
Retiring Gmailify and the POP fetcher will expose senders with misconfigured authentication. Under the new model there is no secondary safety net; messages will be evaluated based solely on their SPF, DKIM and DMARC alignment. The industry is moving from optional “best practices” to binary acceptance or rejection. Google’s bulk‑sender guidelines specify that messages must be authenticated with both SPF and DKIM and that the From header must align with the sending domain. Starting November 2025 Google will increasingly reject traffic that does not meet these criteria. Without the reputation umbrella provided by Gmailify, senders who rely on outdated workflows – such as forwarding through intermediaries that break DKIM signatures – will see higher failure rates. Conversely, organizations that enforce DMARC (p=quarantine or p=reject), sign all mail with durable DKIM keys, and forward mail via ARC‑aware or IMAP mechanisms are better positioned to retain deliverability.
How to Prepare
- Audit your domains – Make sure SPF records are concise and include all legitimate sending IPs, sign all outbound messages with DKIM, and publish a DMARC policy. The Gmail help page clarifies that Gmail will still accept inbound POP/IMAP connections; what disappears is Gmail acting as the POP client.
- Replace POP fetching – Use provider‑side forwarding or add the account to the Gmail mobile app via IMAP; note that forwarding must preserve authentication so that SPF and DKIM remain valid. As Mythic Beasts warns, simple forwarding may cause rejections unless SRS (Sender Rewriting Scheme) is used.
- Monitor policy enforcement – Use Google’s Postmaster Tools and DMARC aggregate reports to monitor rejection rates and adjust promptly. Expect temporary deferrals or outright rejections as enforcement ramps up.
Conclusion
Gmailify’s quiet retirement is not just the end of a convenience feature; it marks the end of an era in which Gmail served as a trust proxy for unauthenticated email. By forcing messages to stand on their own authentication, Google is aligning with a broader industry push that treats email identity as a hard requirement rather than an optional signal. Senders who modernize their authentication practices will adapt smoothly. Those who don’t will find their messages increasingly absent from the inbox.
