Gmail “Send as” ends in January 2027: what to do with your domain email

For years, the easiest way to get a professional address looked like this: register a domain, forward its mail to a free Gmail account, and reply with “Send as” using [email protected]. No extra cost, inside the inbox you already use.

That setup stops working in January 2027. This guide explains exactly what is changing, how to check in two minutes whether it affects you, and the options you have, with honest trade-offs for each.

What exactly is changing

Google has added two separate notices to Gmail Help.

1. “Send as” for third-party addresses. On the page about sending from a different address, Google says that starting January 2027 Gmail will no longer support the “Send as” feature for third-party email addresses. “Third-party” means any address whose mailbox is not run by Google: Outlook, Yahoo, and your own domain if its mail is hosted elsewhere.

2. Gmailify and POP fetching. A second page announces the end of:

• Gmailify, which added Gmail’s spam filtering, inbox categories and faster search to outside accounts;
• “Check mail from other accounts”, Gmail’s POP fetching on the web. After the first quarter of 2026 it no longer supports new users; existing users can keep it until January 2027.

Are you affected? A 30-second check

Open Gmail on a computer and go to Settings (the gear) → See all settings → Accounts and Import.

• Under “Send mail as”, look at the listed addresses. If any of them does not end in @gmail.com and does not belong to a Google Workspace account, you are affected.
• Under “Check mail from other accounts”, any account listed there will stop being fetched in January 2027.

If both sections only show your Gmail address, this change does not affect you.

Who is not affected

Google is explicit: the change does not affect Google Workspace aliases or other Gmail addresses you own. If your domain already runs on Google Workspace and you send from an alias configured there, you don’t need to do anything.

Receiving doesn’t change either. Where your domain’s mail is delivered is decided by its MX records, not by Gmail, so forwarding set up at your domain provider keeps working.

Your four options, compared

Option	What you get	Trade-offs
Google Workspace	Stay in Gmail with your domain address and aliases	A subscription per user: the bill grows with every colleague
Your domain provider’s mailbox	Often included or cheap; can be added to the Gmail app on your phone over IMAP	On desktop you use the provider’s webmail, not Gmail; quality and features vary a lot
Forward to Gmail, reply from @gmail.com	Free, nothing to configure	Customers see your Gmail address, so you lose the professional one
A provider built for domain email (e.g. Nilomail, launching soon)	A mailbox on your domain, a shared inbox for your team, newsletters; priced per domain, with users included in the plan	You use the provider’s own app; your old mail stays in Gmail

How to choose:

• Working solo and mostly replying from your phone? Your provider’s mailbox added to the Gmail app over IMAP, which Google itself suggests, may be enough.
• Want to stay in Gmail no matter what? Google Workspace is the only way. Multiply the per-user price by everyone who needs an address.
• Several people answering the same addresses (hello@, orders@, support@)? You need a shared inbox, not more licences. That is the case we built Nilomail for.

What to do now, in five steps

1. List your addresses

Write down every address you use with “Send as” and who uses it. There are often more than you think: hello@, your name, invoices@, an old project address.

2. Decide what each address needs

A personal address (maria@) needs a mailbox. A shared one (hello@, orders@) needs a shared inbox, where several people see incoming requests, assign them, and never reply twice to the same customer.

3. Prepare your DNS records

Whatever you choose (except staying on forwarding), you’ll change a few records in your domain’s DNS settings:

• MX tells the world where to deliver incoming mail;
• SPF declares which servers may send for your domain;
• DKIM signs your messages so recipients can verify them;
• DMARC tells recipients what to do with mail that fails those checks.

Your new provider gives you the exact values. You don’t need to transfer the domain: you edit the records where they already are.

4. Switch on a quiet day and verify

After changing the MX records, propagation usually takes from a few minutes to a few hours. Then:

• send a test message to a Gmail address and an Outlook address;
• open the received message, view the original headers and check that SPF and DKIM show pass;
• reply to it and confirm the reply lands in the new mailbox.

5. Update signatures and settings

Update your signature, tell regular customers if anything changes for them (usually nothing, since the address stays the same), and remove the address from Gmail’s “Send mail as” list so you don’t use it by mistake.

What happens to the mail already in Gmail

Nothing. Messages you have received, sent or fetched stay in your Gmail account, as Google confirms for anything synced before the deprecation. You can keep searching them whenever you need. The change only affects how you send and receive from now on.

If you want a separate copy of your archive, you can download it with Google Takeout.

When to act

Google only says “January 2027”. Aim to finish by December 2026: that gives you a few weeks to catch a wrong DNS record or a forgotten address before a customer is left without a reply.