Globhy
AllBusinessHealthMarketingTechnologyTravelUncategorized
Posted on 03 Sep 2026Edited on 03 Sep 2026

Share:

Google Is Ending Gmail’s Third-Party “Send As”: What to Do Before 2027

Google Is Ending Gmail’s Third-Party “Send As”: What to Do Before 2027

Google is ending third-party Gmail “Send as,” Gmailify and POP in January 2027. Learn how businesses can migrate securely with SPF, DKIM, DMARC, S/MIME and modern business email.

Google is changing how Gmail handles third-party email accounts, and businesses using Gmail as a front end for non-Google mailboxes need to act before January 2027. Google will remove Gmail’s ability to use “Send as” for third-party email addresses, while Gmailify and web-based POP fetching will also be discontinued. Google Workspace aliases and Gmail-to-Gmail “Send as” are not affected.

For organizations using custom-domain business email, the real question is bigger than Gmail: Where should your business email infrastructure live, who controls it, and how securely is it authenticated and encrypted?

What Is Google Changing in Gmail in 2027?

Starting January 2027, Gmail will no longer allow users to send mail from third-party email addresses through Gmail’s “Send as” feature. Google is also removing Gmailify and web-based POP retrieval for third-party accounts. The transition period runs through Q3–Q4 2026, making this the right time to audit and migrate affected accounts.

What is being discontinued?

Google has announced three related changes:

Gmail feature

January 2027 status

“Send as” using third-party email accounts

Discontinued

Gmailify for third-party accounts

Discontinued

“Check mail from other accounts” using POP on the web

Discontinued

Gmail-to-Gmail aliases

Not affected

Google Workspace “Send as” functionality

Not affected

Third-party accounts in Gmail mobile app

Still supported

Google says affected users can continue using their third-party accounts through a provider's native application, a desktop email client, or the Gmail mobile app.

Why does this matter to businesses?

Many SMEs and startups have historically used Gmail as a convenient interface while their actual mailbox or SMTP infrastructure remained elsewhere.

For example:

employee@company.com → third-party mail server → Gmail interface → customer

If Gmail is being used to send as employee@company.com, the organization may have built an operational dependency around a feature that will no longer exist in January 2027.

Key takeaway: This is not simply a Gmail settings change. For organizations dependent on third-party mail infrastructure, it is an opportunity to reassess email architecture, security, authentication, and data control.

Who Will Be Affected by the Gmail “Send As” Shutdown?

Organizations are affected when Gmail is used to send from an email address hosted outside Google. The impact is especially relevant to companies using custom-domain business email, legacy mail servers, hosted email providers, or hybrid configurations where Gmail is only the user interface rather than the actual email platform.

Definition

A third-party email account is an email account hosted by a provider other than Google, for example, a mailbox hosted on another business email platform or mail server.

Examples

You should investigate your environment if employees currently:

  • Send from name@company.com through Gmail while the mailbox is hosted elsewhere.
  • Use Gmail to send from Yahoo, Outlook or another non-Google account.
  • Fetch messages from an external mailbox using Gmail POP.
  • Depend on Gmailify to provide Gmail features to a third-party mailbox.
  • Use multiple email domains across different providers.

Google specifically notes that third-party “Send as” addresses such as non-Gmail accounts will be affected.

Practical application

Share:

More in Business

View category