Gmailify, POP Fetch and Send As End in January 2027: What Nonprofit Staff Using Gmail Should Change

Gmailify, POP fetch and "Send mail as" for outside addresses all leave Gmail in January 2027, according to a Google help page. Google says it "will fully remove" all three that month. Gmail aliases and Google Workspace addresses are not affected.

This matters most to small nonprofits and associations where staff read their organization’s email inside a free Gmail account. The org mail might live at GoDaddy, Bluehost, a cPanel host or Microsoft 365. Gmail pulls it in and sends replies as the org address. That setup is what ends. This piece covers what stops, when, what still works, and what to use instead.

The short version: check each staff Gmail account for POP fetch, Gmailify or a "Send mail as" address from another provider. If you find one, pick a replacement before January. Forward mail from your host, add the account to the Gmail mobile app over IMAP, use a desktop mail client, or move the domain to Google Workspace or Microsoft 365. Mail Gmail has already fetched stays put.

What Google is removing in January 2027

Google’s help page on third-party account changes lists three features. All three apply only to non-Google accounts, such as Yahoo, Outlook.com or an address on your own domain hosted elsewhere.

Google has not named a day. The page gives the month only. During the current transition period, Google says the features keep working but "Gmail may restrict new configurations." Treat any new setup as unreliable from here on.

Google also notes that you can no longer add or sync a third-party account in Gmail on the web. The web version is not a fallback.

How the Gmailify and POP timeline got here

This is the second notice. In autumn 2025, Google first said Gmailify and POP support would end in January 2026, as reported by Jetstream on October 1, 2025.

Google’s Gmailify and POP help page now gives a later date. It says new users lost access after the first quarter of 2026, and existing users can keep the features until January 2027.

The "Send mail as" change is newer. Google’s timeline puts its announcement in the third quarter of 2026, with in-product notices to affected users. Android Authority reported it on August 5, 2026. Send As, POP and Gmailify now share the same January 2027 end.

What still works after January

Several common setups are untouched. Google’s page lists them directly.

• Gmail and Workspace aliases. Google says “Gmail-to-Gmail aliases and Google Workspace” sending is not affected.
• Forwarding. Your outside provider can still auto-forward mail to your Gmail address.
• The Gmail mobile app. You can still add an outside account to the app on Android, iPhone and iPad.
• POP on Android. Google says the Gmail app for Android keeps POP access to third-party mail.
• Reaching Gmail from other apps. Outlook, Thunderbird and Apple Mail can still read a Gmail account over IMAP or POP.

One gap is worth flagging. Google’s page does not say directly whether a Workspace user who sends as a non-Google address is affected. It says the change "only applies to third-party, non-Google email accounts." If your Workspace staff send as an address hosted elsewhere, ask Google support or your reseller.

Who this hits at a small nonprofit

The common pattern looks like this. The organization owns its domain. Email for that domain is hosted by the web host, a registrar like GoDaddy, or Microsoft 365. A staff member, often the executive director or a part-time bookkeeper, prefers Gmail. So their personal Gmail account fetches the org mail over POP and sends replies as the org address.

After January, three things change for that person:

1. New org mail stops arriving in Gmail.
2. Replies can no longer go out as the org address from Gmail on the web.
3. If the account used Gmailify, the Gmail spam filtering and inbox categories on that account stop.

Volunteer roles are the easy ones to miss. A board treasurer or membership chair with a role address like treasurer@ often set this up years ago. Nobody at the office may know it exists.

How to check for Gmailify, POP and Send mail as

Each person can check in about a minute on a computer. Google’s Send As help page gives the path.

1. Open Gmail on the web and select Settings, then See all settings.
2. Open the Accounts and Import tab (or Accounts).
3. Look at Send mail as. Any address that is not a Gmail or Workspace address is affected.
4. Look at Check mail from other accounts. Any account listed there uses POP fetch or Gmailify.

Make a short list: the person, the address, where the mailbox is hosted, and whether they send as it. That list decides which option below fits.

Option 1: forward from your host

Forwarding is the smallest change for receiving mail. You set it up at the email host, not in Gmail. Look for "forwarding" or "forwarders" in your host’s email settings, and point the org address at the Gmail address.

Forwarding only handles incoming mail. Replies from Gmail will come from the personal gmail.com address. For a board volunteer who mostly reads, that may be fine. For anyone who writes to donors or members, it is not, because the org address is the one people trust.

Check whether your host keeps a copy in the org mailbox after forwarding. Decide whether the org needs that copy for records.

Option 2: add the account to the Gmail app with IMAP

The Gmail app on Android, iPhone and iPad can still hold an outside account. Google’s guide to adding another account says you can add up to five addresses. In the app, open your profile, choose Add another account, and pick the provider or Other (IMAP).

IMAP keeps the mail on the host and syncs it to the phone. Reading and replying both happen against the org mailbox, so sent mail goes out as the org address. You will need the host’s IMAP settings. Some hosts also ask for an app password.

The catch is the computer. This works in the app only, not in Gmail on the web. For desk work, Google points people to the host’s own webmail or a desktop client that supports IMAP and SMTP.

Option 3: move the domain to Google Workspace or Microsoft 365

If several people rely on the old setup, moving the domain is often the cleaner fix. Each person gets a real mailbox at the org address, with sending built in.

Google says qualifying organizations can get Google Workspace for Nonprofits at no charge, through Google for Nonprofits, with discounts on paid editions. Microsoft says it provides grants and discounts for eligible nonprofits on its nonprofit plans page. Check current terms for your country, as of October 2026.

A domain move takes planning. You change MX records in DNS, migrate old mail and retrain staff. Our explainer on what DNS is and how it works covers the records involved. If you land on Workspace, our post on Gmail AI Inbox in Workspace covers the newest Gmail settings admins will see.

Set up SPF, DKIM and DMARC when you send from your domain

Whichever option you pick, check that the domain is set up to send. Gmail’s Send As often sent through the host’s mail server. Now staff may send from webmail, a phone app or a new provider instead.

Three DNS records tell receiving servers that mail from your domain is real:

• SPF lists the servers allowed to send for the domain.
• DKIM adds a signature that receivers can check.
• DMARC tells receivers what to do when the first two fail.

Google’s sender guidelines FAQ requires bulk senders, those sending 5,000 or more messages a day to personal Gmail accounts, to use SPF, DKIM and a DMARC record. Most small nonprofits send far less than that. Setting all three still helps receipts and renewal notices reach the inbox. Our post on email marketing in the AI inbox covers how Gmail and others now sort mail.

Tools like these follow the same pattern as many phishing attacks: they ask for a password or a sign-in grant you would not give a stranger.

What happens to mail Gmail already fetched

Nothing. Google’s FAQ says: "Any messages you’ve already imported from a third-party account into Gmail will remain in your mailbox." Only new fetching and sending end.

That has a records side. Years of org mail may now sit only in someone’s personal Gmail account. If that person leaves, the org loses access. Before January, decide whether those messages should be exported or moved into an org-controlled mailbox.

Similar moves at Microsoft

Google is not alone in closing older mail connections. Microsoft says password-only (Basic Authentication) sign-in stopped working for Outlook.com accounts on September 16, 2024, which broke many POP and IMAP setups in other apps. In Exchange Online, Basic authentication for SMTP AUTH turns off by default for existing tenants at the end of December 2026, according to Microsoft’s Exchange Team. Our Q4 2026 platform calendar covers what that means for website forms. We covered another Microsoft sign-in change in our post on Microsoft’s SMS MFA retirement.

A checklist before January

1. Ask every staff member and volunteer who uses Gmail for org mail to check Accounts and Import.
2. List each affected address, where it is hosted, and whether the person sends as it.
3. Pick one option per person: forwarding, the Gmail app over IMAP, a desktop client, or a new mailbox.
4. If more than a few people are affected, price a move to Google Workspace or Microsoft 365.
5. Check SPF, DKIM and DMARC for the domain before staff change how they send.
6. Turn on your own spam filtering at the host for any account that relied on Gmailify.
7. Decide where old fetched mail should live and move it to an org-controlled account.
8. Send a test message to and from each new setup in December, while the old one still works.

Frequently Asked Questions