Gmail Stops Fetching POP Mail and Ends Gmailify in January 2027: Switch to Forwarding or IMAP
Short answer: Google says existing users can use Gmail's "Check mail from other accounts" (POP) and Gmailify only until January 2027 (no exact day given). After that, new mail from the other account stops arriving in Gmail. Set up forwarding with DKIM on your domain, or read that mailbox over IMAP.
| Who | |
|---|---|
| Status | confirmed |
| Dates |
|
Who is affected
People who use Gmail on a computer to pull mail from another mailbox over POP, often a domain mailbox at a web host, and people who linked another account with Gmailify. Google's notice names only these two features.
What you will see
- New mail from the other account no longer shows up in Gmail. Nothing bounces; the mail stays in the other mailbox. Messages fetched before the change stay in Gmail.
- The "Check mail from other accounts" option is gone from Gmail settings on a computer.
- Accounts linked with Gmailify lose Gmail's spam protection, inbox categories, better mobile notifications and advanced search.
- Expected after a careless forwarding setup: forwarded mail lands in spam, or bounces with 550-5.7.26 Unauthenticated email from domain-name is not accepted due to domain's DMARC policy.
Check your setup today
- In Gmail on a computer, open the settings tab Accounts and Import. If an account is listed under Check mail from other accounts, you are affected.
- Run our checker on that account's domain and read the DKIM line. Google warns that forwarded mail often fails SPF, so a passing DKIM key for your own domain is what keeps it out of spam.
- In the same report, check that SPF and DMARC exist and are valid for the domain.
- Ask your old provider whether its forwarding rewrites the envelope sender to the forwarding domain (often called SRS), filters spam before forwarding, and can add ARC headers.
How to fix it
- Simplest long-term fix: point the domain's MX at a mailbox provider you read directly (for example Google Workspace, Microsoft 365 or Zoho Mail), so nothing has to be fetched.
- Or do what Google suggests: set up automatic forwarding at the old provider to your Gmail address. Have the envelope sender rewritten to the forwarding domain, filter spam before forwarding, and don't change the subject, body or headers on the way, or DKIM breaks.
- Turn on DKIM for your domain at that provider. Keep one SPF record that lists it (SPF generator) and publish DMARC (DMARC generator).
- If the forwarding host can add ARC headers, turn that on: ARC keeps the earlier SPF and DKIM results of a forwarded message.
- Or skip forwarding: on a phone, add the account to the Gmail app (it uses IMAP); on a computer, use any IMAP mail client.
- Google's notice doesn't mention "Send mail as". After switching, send a test reply to confirm it still works.
Check your domain now
After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.
Related pages
- Gmail 550 5.7.26 unauthenticated sender: how to fix
- SPF generator
- DMARC generator
- SPF, DKIM and DMARC for Google Workspace
Sources
- Google: Learn about upcoming changes to Gmailify & POP in Gmail
- Google: Best practices for forwarding email to Gmail
- Google Workspace: ARC email authentication
- Google: Gmail SMTP errors and codes
Other upcoming changes
- Microsoft 365 SMTP AUTH: Basic Authentication Off by Default at the End of December 2026
- DMARCbis (RFC 9989): pct Is Gone, t=, np= and psd= Are New — Update Your DMARC Record
- Shorter TLS Certificates for Mail Servers: Let's Encrypt 64 Days (Feb 2027), 100-Day Maximum (Mar 2027)
- April 15, 2027 Root CA Distrust: Will Your Mail Server's Certificate Still Be Trusted?
- Microsoft 365 MX Records Move to *.mx.microsoft: What Changes for New and Existing Domains
- Outlook "Promotions" Tag in Microsoft 365: What It Means for Your Newsletters and Notifications
- MailerSend Retires DKIM TXT Records on 1 February 2027: Move to the New CNAME Records