Forward email to Slack / Gmail POP and Send as
Gmail is ending POP fetch and "Send as" for other accounts: where support@ goes next
If your team reads a support@ that lives at another provider inside Gmail ("Check mail from other accounts" over POP, or Gmailify) and answers it with "Send mail as", both halves stop working in January 2027, according to Google. Google's suggestion for receiving is automatic forwarding from the other provider. You can forward to RelayMail instead: each email becomes a Slack thread, and replies from the thread go out as email, from support@ once your domain is verified.
Steps
- 1
Check whether this affects you
In Gmail, open Settings > See all settings > Accounts and Import. If "Check mail from other accounts" lists your support address, or you send as an address hosted outside Google, it is affected. Addresses hosted by Google (your Workspace address or its aliases) are not: Google says "Send as" keeps working for Google-hosted identities.
- 2
Turn on forwarding at the provider that hosts support@
Sign in to the provider that hosts the address and set automatic forwarding to the forwarding address on your RelayMail setup page (inbox-...@relay.relaymail.app). The hub page has the click path for each provider, including groups, aliases and shared mailboxes.
- 3
Confirm the forward
If the provider sends a confirmation email, RelayMail passes it on to the email on your Slack account; click its link. Then send a test email from another account: when it arrives, RelayMail confirms forwarding by itself.
- 4
Reply as support@ again
Verify your domain in RelayMail (see the custom domain guide) so replies from the Slack thread go out from support@yourcompany.com. Until then they go out from the RelayMail relay address with Reply-To set to support@, so answers still come back.
- 5
Retire the Gmail POP account
Once email arrives in Slack, remove the account from "Check mail from other accounts" in Gmail so messages are not fetched twice. Mail Gmail already imported stays in Gmail.
Confirming the forward
Google's timeline: Gmailify no longer takes new users after the first quarter of 2026; during Q3 and Q4 2026, "Send as" for third-party accounts, Gmailify and POP keep working; in January 2027 Gmail fully removes all three. Google's suggestion for receiving that mail is automatic forwarding from the other provider, and for sending, the provider's own site or a desktop client over IMAP/SMTP. Forwarding to RelayMail covers both: the team reads and answers in Slack.
What to watch for
- Only mail from third-party accounts is affected. Google says connecting to Gmail itself over POP or IMAP from other apps keeps working, and so does the Gmail mobile app's access to other accounts.
- Replies come from support@ only after your domain is verified in RelayMail. If support@ is on a domain you can't add DNS records to, replies go out from the relay address with Reply-To set to support@.
- Some providers only allow one forwarding address. If people also want the mail in their own inbox, read it in the Slack channel instead, or forward to a group that includes RelayMail.
- Mail that Gmail already fetched stays in Gmail. Only new mail goes to Slack once the forward is on.
Questions
When does Gmail stop supporting POP for other accounts?
Google says Gmail fully removes POP fetching, Gmailify and "Send as" for third-party accounts in January 2027, with Q3 and Q4 2026 as the transition period.
Can I still send as support@ from Gmail after January 2027?
Not if support@ is hosted outside Google. Google says "Send as" keeps working for Google-hosted identities, such as Workspace aliases.
What does Google recommend instead of POP?
Setting up automatic forwarding at the other provider so new mail arrives without POP. Forwarding to RelayMail sends that mail to a Slack channel, where the team can answer it.
Answer Gmail POP and Send as email from the Slack thread
14-day trial, $0 today, then from $15/month per inbox. Cancel in Billing before day 14 and you pay nothing.
See plans and start the trialUpdated 2026-11-07. How we check these pages. Sources: Gmail Help: Changes to third-party email account support, Gmail Help: Upcoming changes to Gmailify and POP, Gmail Help: Check emails from other accounts.
Related
- Forward email to a Slack channel from any provider
- Forward a Cloudflare Email Routing address to Slack
- Forward a Google Group (support@) to a Slack channel
- Forward a Microsoft 365 shared mailbox to Slack
- Forward an ImprovMX alias to a Slack channel
- Forward Zoho Mail (support@) to a Slack channel
- Send a Microsoft 365 distribution list (support@) to a Slack channel
- Forward a Hostinger Email address (support@) to a Slack channel
- Forward a Squarespace domain address (support@) to a Slack channel
- Forward a GoDaddy email address (support@) to a Slack channel
- Forward a Proton Mail address (support@) to a Slack channel
- Forward a Fastmail address (support@) to a Slack channel
- Forward a Namecheap email forwarder (support@) to Slack
- Forward a Porkbun email forward (support@) to Slack
- Send replies from your own domain
- How to reply to email from Slack
- The ways to get a shared inbox into Slack, compared
- Forward a Gmail mailbox to Slack, step by step