GmailGmail shuts down 'Send as', POP, and Gmailify in January 2027: what to do if you use a single inbox for all your addresses
Team at AiToolsForAppsWritten with AI assistance16 min readIn summary
- In January 2027 Gmail removes three things at once for personal accounts: "Send as" from third-party addresses, Gmailify, and mail retrieval via POP in the web version. This is confirmed by the Gmail help page on changes to third-party mail accounts, which sets the announcement in the third quarter of 2026 and complete removal in January 2027.
- What is NOT affected: Gmail to Gmail aliases, Google Workspace's "Send mail as", IMAP/POP access from external clients (Outlook, Thunderbird, Apple Mail), the Gmail API, and —the detail that almost nobody mentions— non-Google accounts within the Gmail mobile app, which according to Google "does not change".
- The press dates do not match: media outlets like ITSitio spoke in February 2026 of a blackout "throughout 2026". The valid reference is the official help: January 2027, with a restriction on new configurations before that date.
- Three exits, all with a toll: switching to Google Workspace (€6.80/user/month on the Starter plan according to the official Google Workspace pricing), setting up automatic forwarding + your own SMTP, or separating mail into different clients.
- The hidden cost is not technical, it is manual: changing mailboxes requires manually rebuilding the signature for each identity (and its plain text version for mobile), the filters and labels that Gmailify previously applied, and the response templates.

If you have been working for years with just one tab open —your personal Gmail collecting mail from [email protected], the old business Hotmail, and the Yahoo account you use for suppliers—, January 2027 is going to break your setup. And what hurts is not the mailbox migration: it is everything that was on top, the signature with the logo, the filters that sorted automatically, the canned responses. At AiToolsForApps, we set up tools for that manual part; in fact, aiGmail was born just for that, and further down you'll see where it fits. But first, the verifiable facts: what is shutting down, when, and what alternatives hold up.
This article is not a product manual. It is the real state of the matter as of November 14, 2026, with the dates checked against the official notice from Google, because the versions circulating out there contradict each other.
What exactly is Gmail removing in January 2027?
Gmail is removing three distinct functions in January 2027 that many people used together: "Send as" from third-party addresses, Gmailify, and mail retrieval from other accounts via POP on the web. The official Gmail help groups the last two under the heading "Gmailify & POP on the web" and places the total removal in January 2027, following a transition period in the third and fourth quarters of 2026 during which the functions remain active but Google "will restrict new configurations".
It is advisable to separate them, because each one solved a different problem:
- Third-party "Send as": allowed you to write from Gmail and have the recipient see
[email protected]or[email protected]as the sender. The Gmail help on sending from other addresses already warns on its own page: "Starting in January 2027, Gmail will no longer support the "Send as" feature for third-party email addresses, such as @yahoo.com or @outlook.com". - POP ("Check mail from other accounts"): Gmail would periodically connect to the external provider's server, download the messages, and leave them in your inbox.
- Gmailify: the upper layer. It applied Google's spam filter, inbox classification, and search to those external accounts. It was the reason why your Hotmail "behaved well" within Gmail.
The reassuring detail: the mail you have already imported will not be deleted. Google states this explicitly: "Any messages you've already imported from a third-party account into Gmail will remain in your mailbox". What stops working is future synchronization and sending.

Why do some sources say "late 2026" and others "January 2027"?
Because the news leaked in phases and the press covered different phases. In February 2026, ITSitio reported on a gradual dismantling of Gmailify and POP "throughout 2026," starting in the first quarter. In August 2026, Autónomos y Emprendedor already cited January 1, 2027, as the effective date. Both statements were true at the time: first, the entry of new configurations was cut off, and then the final shutdown was announced.
The practical rule to avoid mistakes: the date that matters is the one in Google's help article, and that article states January 2027. If you are planning the migration of a client or your own business, cite that page and not a press release.
| Milestone | Date according to Google's official help | What it implies |
|---|---|---|
| Announcement and notices within the product | Third quarter of 2026 | You start to see the notice in Gmail |
| Transition period | Q3–Q4 2026 | Everything continues to function, but new configurations are restricted |
| Complete withdrawal | January 2027 | Third-party "Send as" stops working, Gmailify and POP on the web |
| Already imported mail | No date: remains | Downloaded messages stay in your inbox |
Source: Gmail Help — changes in compatibility with third-party email accounts, consulted on November 14, 2026.
What continues to work after January 2027?
Much more continues to work than what the headlines suggest: Gmail to Gmail aliases, Google Workspace's "Send mail as," IMAP and POP access from desktop clients, the Gmail API, automatic forwarding from the external provider to Gmail, and —this is key for those who work from their phones— non-Google accounts added in the Gmail mobile app.
The last one is the most overlooked note by the coverage in Spanish. Google's help states it unequivocally: "Access through the Gmail mobile app for Android, iPhone, and iPad will not change. You can continue to add and use non-Google accounts in the Gmail mobile app as you do today." In other words: what is shutting down is the setup of Gmail web over third-party accounts, not the mobile app, which functions like any IMAP client.
| Function | Survives January 2027? |
|---|---|
| Alias from one Gmail account to another Gmail account | Yes |
| "Send mail as" in Google Workspace | Yes |
| Non-Google accounts in the Gmail mobile app | Yes, "does not change" |
| IMAP/POP from Outlook, Thunderbird, or Apple Mail | Yes |
| Automatic forwarding from the external provider to Gmail | Yes |
| Gmail API | Yes |
| "Send as" from a third-party address in Gmail web | No |
| POP retrieval from external accounts in Gmail web | No |
| Gmailify over external accounts | No |
Why is Google shutting it down? The answer lies in authentication
The underlying reason is email authentication. When Gmail sent a message "as" [email protected] through its own servers, it signed with an identity that did not correspond to the sender's domain, and that directly clashes with the SPF/DKIM/DMARC model that Google itself has imposed on the rest of the market.
Google's guidelines for email senders require as of February 1, 2024, that every sender has SPF or DKIM, and that anyone sending more than 5,000 messages a day to Gmail accounts has SPF, DKIM and DMARC, with the explicit consequence that non-compliant emails may be rejected or end up in spam. A "Send as" that routes through Google's servers a domain that Google does not control is exactly the type of configuration that those rules were meant to regulate.
Translated to your day-to-day: even if the function still existed, the deliverability of emails sent this way had been worsening for years. If you were sending through Gmail's servers instead of your domain's SMTP, you were likely already seeing the "on behalf of" in some clients and more messages in spam than usual.
How many people does this really affect?
There is no official figure from Google, but the affected profile is huge and very identifiable: the self-employed or micro-business that uses Gmail as a hub for various addresses. In Spain, the RETA surpassed 3.5 million affiliates for the first time in October 2026, and a good part of that group has never paid for corporate email: they have the domain on a hosting service and read it from Gmail.
Regarding specific magnitudes, one must be cautious. Autónomos y Emprendedor, in its article from August 29, 2026, states that "about 50% of professionals" use these configurations; it is an estimate from the medium, not an audited figure from Google, and it is advisable to cite it as such. What is measured is Gmail's weight as a reading client: the email client market share from Litmus gave it a 17.02% share of opens in October 2026, behind Apple (75.84%) and ahead of Outlook (3.49%).
The three options, with their downsides
There are three realistic paths and none are free: switch to Google Workspace, set up automatic forwarding plus your own SMTP, or separate the email into different clients. The choice depends on whether you care about keeping a single inbox, retaining the domain, or not paying.

Option 1: switch your domain to Google Workspace
This is the path with the least conceptual friction: you keep Gmail as you know it and the "Send mail as" feature is still supported. According to the official Google Workspace pricing, Business Starter costs €6.80/user/month with 30 GB of storage, Standard €13.60 with 2 TB, and Plus €21.10 with 5 TB (prices checked on November 14, 2026; the annual commitment saves 16% compared to the flexible plan, and all three plans support up to 300 users).
The downsides: (1) it becomes a recurring expense for each mailbox, not per business; (2) you have to touch the MX records of your domain, which means a window where email can bounce if you make a mistake; (3) it does not resolve inherited Hotmail or Yahoo accounts —those remain third-party addresses—; and (4) if you want Workspace to send through another provider's SMTP, the per-user outbound gateway option must be enabled by an administrator from the console: "The user only has the option if you allow it from the Google Admin Console."
Option 2: automatic forwarding to Gmail + own SMTP for sending
This is the one that keeps the single inbox without paying for Workspace, and it is an alternative that Google explicitly acknowledges: "You can configure your third-party provider to auto-forward messages to your Gmail address." You receive everything in Gmail via forwarding from your hosting panel, and to reply you use the provider's client or your own SMTP.
The downsides: (1) you configure the forwarding with your provider, not in Gmail, so each domain and each inherited account is handled separately; (2) the forwarded email may lose some of its original authentication and spam filters treat it worse; (3) and the big one: you receive in Gmail but cannot reply from Gmail web with that identity. The reply has to come from another place, which splits your workflow in two.
Option 3: separate email clients
You leave Gmail for what it is Gmail and open each external account where it belongs: the provider's webmail, a desktop client via IMAP/SMTP (Outlook, Thunderbird, Apple Mail), or the mobile Gmail app, which still accepts non-Google accounts. This is Google's literal recommendation and it is the zero-cost option.
The downsides: (1) goodbye to the single inbox —you have to check multiple sites again—; (2) you lose Gmail's search and categorization over that email, which was exactly what Gmailify provided; and (3) each client has its own system of signatures, filters, and templates, which multiplies the configuration work by the number of programs.
| Option | Cost | Keeps single inbox | Can send with your identity | Main downside |
|---|---|---|---|---|
| Google Workspace | From €6.80/user/month | Yes | Yes (own domain) | Recurring expense and MX change; does not cover inherited Hotmail/Yahoo |
| Forwarding + own SMTP | €0 (plus what you already pay for hosting) | Yes, for receiving | No from Gmail web | Split workflow: you receive in one place, reply in another |
| Separate clients | €0 | No | Yes | Multiply signatures, filters, and templates by each client |
The checklist of what to rebuild manually
Whichever option you choose, what does not migrate automatically is the configuration layer: signatures by identity, plain text signature for mobile, filters, labels, and response templates. No migration assistant copies these for you, and that's where the real hours go.

1. One signature for each surviving identity. If you previously had a single signature because everything came from the same inbox, now you need one per mailbox and per role. And you need the HTML to be simple: plain tables, no modern CSS, because each email client trims as it pleases.
2. The plain text version of that signature, for mobile. This is the step that everyone skips. Gmail on Android and iOS uses a different signature than the web (Settings → your account → Mobile signature) and does not understand HTML. If you don’t write it, the mobile will send without a signature or with the manufacturer’s one.
3. The filters and labels that Gmailify used to handle. This is what you notice the most the next day. The automatic classification disappears, so you have to rewrite the rules manually using Gmail's search syntax (from:, to:, subject:, has:attachment, larger:10M) and redo the label tree, with its levels and colors.
4. The response templates. Estimates, the "received, I’ll reply on Monday", the vacation notice. If they lived as pre-designed responses in an account you are going to abandon, they stay there.
5. The legal block, if you are doing prospecting. When changing mailbox and sender, it is advisable to check that commercial emails still carry sender identification, the reason for contact, and an easy and visible unsubscribe option.
This is where aiGmail fits in, the AiToolsForApps tool for this part of the work. It does not connect to your mailbox or request Google permissions —it does not access your email—: what it does is build the material that you then paste. It assembles the HTML signature from a style catalog, checking the contrast of the accent color on light and dark backgrounds with the WCAG calculation, and simultaneously generates its plain text variant for the mobile signature. It brings recipes for filters with the literal Gmail search already written and its label tree, and exports them as a mailFilters.xml file that Gmail imports all at once. And it has response templates by sector with blanks that are filled in with your data, as well as an anti-spam audit of the text and a cold email sequence generator with GDPR block. You can see it in AI tools for signatures, filters, and cold email in Gmail.
What to do now, with a calendar
There are less than two months until January 2027, and Google’s advice for this period is explicit: "You are encouraged to migrate during this timeframe." If you leave it for the shutdown, you will miss the chance to test calmly.
- Inventory (one hour). Open Settings → Accounts in Gmail web and note each address in "Send mail as" and "Check mail from other accounts." Those are the ones that will die.
- Decide on an exit for each address. It doesn’t have to be the same for all: the custom domain requires Workspace or its own SMTP; the Hotmail from 2009 probably just needs forwarding.
- Export your current configuration before touching anything. Gmail allows you to download filters from Settings → Filters and blocked addresses; also save the HTML of your signatures and the text of your templates.
- Rebuild the configuration layer at the destination following the checklist above, mobile signature included.
- Test sending and check the header. Send yourself an email to another account and check in the original message that SPF and DKIM pass and that there is no "on behalf of" appearing.
Frequently Asked Questions
Does Gmail stop working in January 2027?
No. Gmail continues to function the same for @gmail.com accounts and for Google Workspace. What is being removed is the support for third-party email accounts within Gmail web: "Send as" with external addresses, Gmailify, and POP retrieval.
Will I lose the emails I already downloaded from my Hotmail account or my domain?
No. Google's help is explicit: messages already imported from a third-party account remain in your inbox. What stops is future synchronization.
Can I still read my own domain email from the Gmail app on my mobile?
Yes. According to the official Gmail help, access through the Gmail mobile app for Android, iPhone, and iPad "does not change," and you can continue adding and using non-Google accounts as before. The change affects Gmail on the web.
How much does it cost to switch to Google Workspace to keep "Send as"?
The Business Starter plan is €6.80/user/month according to the official Google Workspace pricing consulted in November 2026, with 30 GB per user. Standard goes up to €13.60 and Plus to €21.10. Note: you pay per inbox, not per company.
If I use automatic forwarding, can I reply from Gmail with my domain address?
Not from Gmail web once "Send as" for third parties is removed. You can receive via forwarding, but to reply with that identity you will need to use the provider's webmail, a desktop client via IMAP/SMTP, or the Gmail mobile app.
Why do some news say 2026 and others January 2027?
Because the process had two phases: first, new configurations were restricted (which the press covered in early 2026), and later the total removal was announced. The valid reference date is that of Google's help article: January 2027.
Do I need to redo filters and labels when changing inbox?
Yes, and this is the most time-consuming part. The classification provided by Gmailify does not migrate, so you need to rewrite the rules with Gmail's search syntax and redo the label tree in the destination inbox. It can be expedited by importing a mailFilters.xml file with the rules already prepared.
Do I have to create a different signature for mobile?
Yes, if you want emails sent from your phone to be signed. The mobile Gmail app has its own signature setting, does not support HTML, and does not inherit the signature from the web: you need a plain text version, short and readable.
Email is fixed once; configuration, every time
The difficult part of this change is not technical: it forces you to manually redo a setup that has been working on its own for years. The inventory and the decision to exit are yours, but the signature by identity, its plain text version for mobile, the filters with their label tree, and the response templates are mechanical work, and that can indeed be expedited. That's what aiGmail from AiToolsForApps is for: you can set up your signatures, filters, and templates for Gmail without granting access to your inbox and without registering to get started, and take away the HTML, the plain text, and the mailFilters.xml ready to paste into the new inbox.
Set up your signature by identity, its plain text version for mobile, filters with its label tree, and your response templates before switching mailboxes. Try it for free at aiGmail, no registration and no access to your email required.
Set up your signature by identity, its plain text version for mobile, filters with its label tree, and your response templates before switching mailboxes. Try it for free at aiGmail, no registration and no access to your email required.Keep reading
View all articles →
Why Your Emails End Up in Spam in Gmail (and What Changed: Now They Are Rejected, Not Filtered)

Broken Geode in Geometry Dash 2.2091: which mods are not working and how to keep creating

DLS 27 in December 2026: what is confirmed, what is not, and what happens to your club, your squad and your kits when you update
