Gmail Is Ending Third-Party “Send As” and POP Fetching: Your Options Before January 2027

If Gmail is the place where you collect mail from several providers, your setup may need to change before January 2027. Google is retiring Gmailify, continuous POP fetching from other accounts, and “Send as” for third-party addresses.

This is a change to how Gmail handles accounts hosted elsewhere. Your Gmail address is not closing. You can still connect an external email client to Gmail. The useful question is which part of your daily workflow depends on Gmail acting as the middleman.

Which connections are affected?

Google’s current transition guide gives January 2027 as the removal date. During the transition, existing setups can continue working, but Google may restrict new configurations.

• “Send as” for third-party addresses: sending through your primary Gmail account using a non-Google address is being removed.
• POP fetching: Gmail on the web will stop continuously pulling messages from another provider.
• Gmailify: Gmail’s extra inbox features for linked third-party accounts are going away.

Google-hosted aliases and Google Workspace “Send as” remain supported. Previously imported messages remain in Gmail. External clients can still access Gmail through IMAP, POP, or its API. See Google’s Gmailify and POP FAQ for the updated timeline.

Start with an inventory of your addresses

Write down every address you receive mail at and every address you send from. For each one, identify the actual hosting provider. A custom business address may be hosted by Google Workspace, Microsoft, or an independent mail host; the domain alone does not tell you which changes apply.

Then check whether incoming messages arrive through forwarding, POP fetching, or a direct account connection. These routes can look identical in the inbox. Also check the address selected when replying: receiving a forwarded message does not automatically give you a replacement way to send from its original account.

Choose a replacement that covers both reading and sending

The provider’s own website is a straightforward option if you only use one other account. A desktop client is useful when several addresses belong in one place: it connects to each provider directly and lets you select the correct account when composing a message.

Forwarding can preserve an incoming stream to Gmail, but treat outgoing mail as a separate decision. Avoid assuming that a forwarding rule will replace “Send as.” Test a reply to someone outside your organization and inspect the sender address they actually receive.

Test the new setup before removing the old one

1. Connect each account to your chosen client using the provider’s supported sign-in method.
2. Send and receive a test message for every address. Check replies as well as new messages.
3. Locate Sent, Drafts, Archive, and custom folders. Confirm that you are looking at the expected account.
4. Check signatures, default sender choices, filters, and forwarding rules.
5. Save an independent copy of important mail and verify that attachments open.

Running old and new routes together can create duplicate deliveries. Once testing is complete, remove redundant forwarding or fetching rules deliberately, keeping a record of what you changed.

Onde o MailVault se encaixa

MailVault lets you work with multiple accounts in one desktop app, including Gmail and Microsoft sign-in plus other IMAP providers. Messages you archive are saved on your disk as standard .eml files. That gives you a portable copy alongside the live account.

Choose the download mode deliberately. A recent-mail cache is useful for everyday work, but it is not proof that every historical message has been saved. For a complete transition, use an explicit backup or archive workflow and verify the result. Our provider migration checklist explains what to check.

Written October 1, 2026. Provider features and availability may change; check the linked official guidance before changing your setup.