site.support.google.com: Gmail ends POP fetching, Gmailify and Send as for other addresses

What Google's help pages say is ending, when, and what keeps working, and how people who read several domains in one Gmail inbox can restructure.

Published by
MarkRelay Research
Updated
Sources
5 primary sources, linked below

Summary

Google is removing three features Gmail users relied on to manage other addresses: fetching mail from other accounts over POP ("Check mail from other accounts"), Gmailify, and "Send as" for third-party addresses. New users lost POP and Gmailify after the first quarter of 2026; existing users keep them until January 2027, when all three are fully removed. IMAP, POP and the API for reading Gmail from other apps stay, and Workspace aliases are not affected. For anyone who collected several domains into one Gmail inbox, that setup ends. One replacement is a multi-domain inbox in your own Cloudflare account: MarkRelay receives every domain through Email Routing, keeps the mail in your D1 and R2, and replies from each address through Email Sending.

Key findings

  1. 1Ending in January 2027: Gmail fetching mail from third-party accounts over POP, Gmailify, and "Send as" for third-party addresses.
  2. 2POP fetching and Gmailify stopped accepting new users after the first quarter of 2026; existing users keep them until January 2027.
  3. 3Google set Q3 2026 for in-product notices about Send as, and Q3–Q4 2026 as a transition in which the features keep working but new setups may be restricted.
  4. 4Not changing: IMAP, POP and the API for reading Gmail in other apps; the Gmail mobile app's access to other accounts; Send as for other Gmail addresses and Workspace aliases; mail already synced.
  5. 5Google's suggested replacements: automatic forwarding from the other provider, the Gmail mobile app over IMAP, the provider's own site, or a desktop mail client.

Questions this report answers

Asked by real people, quoted as they wrote them.

“Gmail sunsetting POP3 – How should I restructure my multi-domain email setup?”

r/smallbusiness

Gmail is ending POP fetching and Gmailify, and in January 2027 also Send as for addresses it does not host. Google's own suggestions are forwarding into Gmail or reading each account in the Gmail mobile app or a desktop client. To keep every domain in one inbox and reply from each, the domains need a host that serves all of them: Google Workspace with secondary domains, a provider such as Fastmail, or a multi-domain inbox in your own Cloudflare account such as MarkRelay.

“Fastmail good alternative to Gmail which is removing “Send As” feature?”

r/fastmail, 23 comments

Google's help pages confirm that Send as for third-party addresses ends in January 2027. Any host that both receives and sends for your domain replaces it; Fastmail's plans with custom domains do, and so does MarkRelay on Cloudflare Email Routing and Email Sending.

“Domain at cloudflare, send email from hello@mydomain.com via gmail?”

r/CloudFlare

Until January 2027, through Gmail's Send as with an SMTP server. After that, Gmail stops Send as for addresses it does not host, so a domain forwarded from Cloudflare Email Routing needs its own sending path, such as Cloudflare Email Sending.

“Using "send as" feature with gmail from custom domain not hosted by Google fails SPF and DKIM”

Super User

Beyond the SPF and DKIM problem, this setup has an end date: Google's Send as help page says Gmail will no longer support Send as for third-party addresses from January 2027.

What changes in Gmail

Check mail from other accounts (POP fetching)

Status
Ending
Date
No new users after Q1 2026; removed January 2027

Gmailify for third-party accounts

Status
Ending
Date
No new users after Q1 2026; removed January 2027

Send as for third-party addresses

Status
Ending
Date
Notice from Q3 2026; removed January 2027

IMAP, POP and API access to Gmail from other apps

Status
Continues
Date
Not stated

Gmail mobile app access to other accounts

Status
Continues
Date
Not stated

Send as for Workspace aliases and other Gmail addresses

Status
Continues
Date
Not stated

Source: Changes to third-party account support, Changes to Gmailify and POP.

Ways to keep several domains in one inbox after 2027

Receive every domain in one place

Forward into Gmail
Yes
Workspace secondary domains
Yes
MarkRelay
Yes

Reply as each domain's address

Forward into Gmail
No: Send as for third-party addresses ends
Workspace secondary domains
Yes
MarkRelay
Yes

Cost

Forward into Gmail
Free
Workspace secondary domains
$7 per user a month, every user on a secondary domain is a seat
MarkRelay
$99/year + $5/month, no per-user fee

Where mail is kept

Forward into Gmail
Your Gmail
Workspace secondary domains
Google
MarkRelay
Your Cloudflare D1 and R2

Apps and AI agents

Forward into Gmail
Gmail API
Workspace secondary domains
Gmail API
MarkRelay
HTTP API, signed webhooks, MCP

Source: Workspace domains, Cloudflare Email Service pricing.

Why forwarding alone is not enough

Google's first suggestion is to forward mail from the other provider into Gmail. That keeps receiving working, but it does not let you answer as that address once Send as for third-party addresses is gone in January 2027. Anyone who answers customers from info@ on one domain and support@ on another needs a host that sends for those domains too.

How MarkRelay keeps several domains in one inbox

MarkRelay runs as a Worker in your own Cloudflare account. Each domain's Email Routing rule, or a single catch-all rule, hands incoming mail to that Worker, which files it into the right mailbox and stores the message and attachments in your D1 database and R2 bucket. Replies go out through Cloudflare Email Sending from the same address, and land back in the same mailbox.

Because the mailboxes live in one app, a team sees every domain in one webmail, while each member sees only the mailboxes granted to them. Apps and AI agents reach the same mailboxes over an HTTP API or the built-in MCP server, with keys limited to chosen mailboxes. What it does not offer is IMAP: you read mail in the browser or through the API.

Where MarkRelay fits

A good fit when

  • Several domains you answer from, now collected in Gmail through POP or Send as.
  • Domains already on Cloudflare, where Email Routing is free and unlimited.
  • A team or AI agents that need the same mailboxes without sharing one Gmail login.

Look elsewhere when

  • Reading the mail in Outlook, Apple Mail or a phone's mail app over IMAP.
  • One address you only read and never answer: forwarding into Gmail is enough.

Common questions

When does Gmail stop POP fetching and Gmailify?

New users lost them after the first quarter of 2026; existing users keep them until January 2027, when Google fully removes them.

Can I still use IMAP with Gmail?

Yes. Google says IMAP, POP and the API remain supported for reading Gmail from other apps; only Gmail fetching other accounts is ending.

Sources and method

  1. Changes to third-party account support (support.google.com/mail/answer/17101213)
  2. Changes to Gmailify and POP (support.google.com/mail/answer/16604719)
  3. Send emails from a different address (support.google.com/mail/answer/22370)
  4. Workspace domains (knowledge.workspace.google.com/admin/domains/add-a-user-alias-domain-or-secondary-domain)
  5. Cloudflare Email Service pricing (developers.cloudflare.com/email-service/platform/pricing/)

Facts are taken from each vendor's own pricing pages, documentation or terms as of the updated date above; prices are in US dollars per month unless stated. Cost comparisons apply each vendor's published rates to the same volume. MarkRelay is not affiliated with Google;"site.support.google.com" in the title names the site these facts come from. MarkRelay sells a self-hosted email app, which this page mentions where it fits. Spotted something outdated? Tell us.

Revisions

  • : First published; every fact checked on the vendor's own pages.

Related guides

More research