4 ms·

You can add your custom domain as an alias on your free Gmail account. That is my setup. Works perfectly.

• comeonppl 5y ago
  Which is absolutely not even remotely close to being the same as your custom domain being a Google OAuth provider. The question stands - hard to imagine how it won't require action on users' parts. And even in the context of this thread, having a sending alias doesn't magically make you able to check mail on a domain you don't control... having a forward alias means nothing in this context. Examples: * If anyone were using a paid Tailscale plan with a free GSuite account, they're probably just hosed. I have no idea how they're going to migrate short of Tailscale extending their auth mechanisms. * Anyone "logging in" with a custom domain email might need to click a link to finish logging in. Unless your GSuite admin migrates mail services manually, you're not getting that email.
  • tssva 5y ago
    When Google announced the shutting down of legacy Gsuite they stated that authentication based upon the legacy accounts would continue to work. As would access to apps and media purchased under that account. Hopefully this will continue to be the plan if one doesn't take advantage of the migration tool.
• anotherman554 5y ago
  Are you paying for email hosting on the custom domain and forwarding the received emails to Gmail? If so that doesn't really solve the problem of the product no longer being free anymore, you now have to pay for email hosting...
  • jonp888 5y ago
    Google is entitled to stop offering a specific feature if they want. The outcry was because they did not offer any migration strategy for accounts that had been created under the free GSuite offer - it was either pay up, or have the account and all associated data be deleted across all Google services.