If you reply to customers from your own domain inside a free Gmail inbox, that setup stops working in January 2027. Google is removing “Send mail as” for third-party addresses, along with Gmailify and POP fetching. Here is what is changing, how to check whether it affects you, and how to move your business email before the deadline instead of after it.
Plenty of small businesses run their email this way. The domain and mailbox live with a web host, and Gmail is just the window: it pulls mail in with POP and sends replies out through the host’s SMTP server using “Send mail as”. It is cheap and familiar, and according to Google’s own help page, it is going away. With Black Friday nine days out, nobody wants to rebuild email this month, but a change like this is easiest to handle while it is still a choice and not an outage.
What Google is changing
Google’s help page “Learn about changes to third-party email account support in Gmail” sets out the timeline:
- Starting January 2027, you will no longer be able to send mail from third-party (non-Google) email accounts in Gmail on the web or in the Gmail mobile apps.
- Gmailify and POP fetching from other accounts are removed on the same schedule, so the “Check mail from other accounts” option disappears from Gmail on the computer (see Google’s Gmailify and POP page).
- During the transition period before then, the features keep working, but Gmail may restrict new setups.
What is not affected: other Gmail addresses, and “Send as” aliases inside a paid Google Workspace account. Mail you have already imported stays in Gmail.
Check if this affects you
It takes about two minutes. Open Gmail on a computer, go to Settings, then “Accounts and Import”.
- Look at “Send mail as”. If your business address (for example
you@yourshop.com) is listed and it is not hosted by Google, your replies are on the clock. - Look at “Check mail from other accounts”. If your domain is listed, incoming mail stops arriving in Gmail in January too.
- Ask everyone on the team to check their own account. Shared inboxes like sales@ or support@ are the ones people forget.
If both sections are empty, you are fine.
Sort your email into three kinds first
Before choosing a fix, separate what you actually send. Each kind needs a different path.
- Conversations: one-to-one replies to customers, suppliers and leads.
- Transactional mail: order confirmations, password resets, invoices and receipts sent by your website, store or app.
- Campaigns: newsletters, offers and announcements sent to a list.
Only the first kind belongs in a mailbox. If anyone on your team has been sending newsletters or bulk follow-ups by hand from Gmail, this is the moment to stop. Personal mailboxes are not built for list sending: they give you no proper unsubscribe handling, bounce reports or sending speed control, and that is a fast way to end up with the problems described in why bulk emails go to spam.
Your options for everyday conversations
Google’s help page lists the paths it recommends:
- Use your email provider’s own webmail or app.
- Use a desktop mail app set up with IMAP for reading and SMTP for sending. Google suggests this if your business relies on “Send as”.
- On a phone, add the account directly to the Gmail app.
- Host your domain’s mailboxes in Google Workspace, which keeps “Send as” for aliases. This is a migration, not a settings change.
Google also warns against third-party tools or browser extensions that promise to bring “Send as” back. They often ask for your password or account tokens, and Google says it cannot guarantee their safety. Do not hand your mailbox to one of these to save an afternoon.
Move website and campaign mail to a real sending setup
This is the part most guides skip. If your store’s receipts or your contact form were quietly going out through the same mailbox you read in Gmail, give them their own route now.
Step 1: Create SMTP credentials for your apps
Pick an SMTP relay or sending service and create SMTP credentials for your website, store or CRM. If you are unsure which model fits, our guide to SMTP server vs SMTP relay explains the difference.
Step 2: Authenticate the new sending path
Add the new service to your domain’s SPF record, publish its DKIM key, then set a DMARC record. If you only change the mail app and keep the same SMTP server, no DNS change is needed. If the sending server changes, your records must cover the new path.
Step 3: Test before you switch
Send a test to a Gmail address and a few other inboxes, open the message headers, and confirm SPF, DKIM and DMARC all pass. Our free online SMTP server test can confirm the connection works first.
Step 4: Give campaigns their own tool
Move newsletters and offers to a proper email marketing tool with lists, unsubscribe links, scheduled sends and bounce reports. Our guide to choosing the best bulk email service for small businesses covers what to look for.
At SMTPProvider, this is what our SMTP relay service is for: authenticated SMTP credentials for websites, CRMs and apps, plus SPF, DKIM and DMARC setup with verification, and a real person on live chat or phone if a DNS record will not validate.
A simple migration checklist
- This week: run the two-minute check above for every team member.
- Before Black Friday: change nothing on live campaigns. Just write down which address sends what.
- Early December: set up the replacement for conversations (webmail, desktop app or Workspace) and test replies from every shared address.
- Mid December: move website, store and CRM mail to SMTP credentials on an authenticated sending service. Test receipts end to end.
- Before January: if you used POP fetching, set up forwarding from your host to wherever you will read mail, and update any internal notes that tell staff to “check Gmail”.
A quick reality check:
Bad: “It still works today, we’ll fix it when replies start failing.”
Good: “Replies come from a desktop app over SMTP, receipts go through an authenticated relay, and campaigns run from a tool built for lists.”
The short version
Gmail is removing “Send as”, Gmailify and POP fetching for non-Google accounts in January 2027. Check Settings, then Accounts and Import, today. Split conversations from transactional and campaign mail, and give each one a proper, authenticated route before the deadline.
If your website or store mail needs a new home, set up authenticated sending with our SMTP relay service.