What alternative solutions would people who use a lot of aliases at their own domain name suggest?
Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
121–130 of 139 posts
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#122This only impacts Gmail web interface, according to [1]. You can use a desktop email client and continue to receive and send email from your custom domain. "Web access changes: As previously announced, you can no longer add or sync your third-party email account in Gmail on the web. Alternative access: To access your third-party email account, you can use a dedicated mail app, a desktop mail client, or the Gmail mobi…
That is basically just saying "the gmail app can be a smtp/imap client for a 3rd party mail provider". It's not really using gmail as when the gmail app is operating in this mode there's a tone of gmail features you don't get.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#123Earlier quoted context omitted.
Before you do that: Consider a more open and transparent email platform such as Proton, Fastmail, Runbox, Tuta, basically just reconsider moving from one evil, unaccountable platform to another. As you may find the evil, unaccountable platform may do evil and unaccountable things.
Tuta is effectively useless without any support for IMAP/SMTP. Bought subscription for a year just to get hit with this artificial limitation.
“Artificial limitation.” So you bought a sub for an E2EE service and are surprised when it doesn’t work with a protocol directly at odds with E2EE…
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#124Regarding the outrage in this thread: Am I missing something? DMARC/SPF/DKIM enforcement makes third-party relaying fragile and likely to cause deliverability failures. Discontinuing it seems like progress towards reducing abuse. Where am I wrong on this?
I bet you there's a lot of people on HN that
1. want their email on their own domain (for professionalism and portability)
2. Want to use Gmail (it is actually a pretty nice service to use)
3. Don't want to use Google Workspace (either because of how cobbled google features are on workspace, because they don't want to migrate google accounts, or because of it's cost)
Google just killed the ability to meet those three requirements. There's lots of people facing either a) showing the world a gmail.com address, b) switching to a different mail solution or c) paying for workspace and accepting it's flaws. It's totally fair for people to be mad about that.
If the "new" infrastructure doesn't support a common and reasonable use case, then perhaps it needs more work.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#125I am not technical. What does this mean for one who migrated to Proton but has their old Gmail account forward to a new Proton address? I am guessing that's unaffected and it's just outbound from Gmail as a third-party email domain?
Yes, that's unaffected
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#126This only impacts Gmail web interface, according to [1]. You can use a desktop email client and continue to receive and send email from your custom domain. "Web access changes: As previously announced, you can no longer add or sync your third-party email account in Gmail on the web. Alternative access: To access your third-party email account, you can use a dedicated mail app, a desktop mail client, or the Gmail mobi…
That is basically just saying "the gmail app can be a smtp/imap client for a 3rd party mail provider". It's not really using gmail as when the gmail app is operating in this mode there's a tone of gmail features you don't get.
I think mainly your mail won't go into the sent folder and be searchable. You can work around that by CCing your domain.
What other features will you not get? The mail composer in Gmail is pretty sucky anyway. For example when you are replying on a long thread it is very hard to see the message you are replying to.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#127This is really obnoxious. I've used this feature for a couple of decades so that my email is not beholden to Google in case I decide to stop using them someday. I guess that day is coming sooner than I had thought.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#128> You can continue to use "Send as" for any Google-hosted identities, including other Gmail addresses or aliases associated with your Google Workspace account. The discontinuation will not impact these addresses, which only applies to third-party, non-Google email accounts.
I have "Send as" accounts that have this configuration:
Mail is sent through: smtp.gmail.com
However the actual email addresses are often custom domains with say both google and cloudflare sfp records with cloudflare handling the incoming emails and forwarding them to gmail with gmail handling outgoing via google's own smtp server directly.
They aren't remotely clear if this use case is considered a third-party, non-Google email account or a Google-hosted identity since the outgoing smtp server being used is still a google server.
It's crazy that they don't actually explain what "any Google-hosted identities" means.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#129Earlier quoted context omitted.
Ignoring how the sausage is made is how people repeat the same mistakes, over and over, in domains as diverse as government, tech, employment, and automobiles. I get that not everyone has the bandwidth or capability to dig into things on their own, but we live in a hostile environment, and we have to either acknowledge that and plan for it, or touch the hot stove over and over again.
You hosting your own phone service too? Everybody has a limit.
What phone service? I have not had a cellular plan of any kind in over 6 years and travel the world, have an active social life, and run businesses without issue. Wifi is just fine and everywhere. I do not need to be communicating with people while driving. Prime thinking time.
People make all sorts of excuses, but at the end of the day cell networks and the attention, privacy, and sovereignty losses that come with them, are optional. There are -always- alternative paths if you ask, and I do not mind being "that guy" to ensure those paths exist for others that need them more than me and lack the privilege to demand them.
Also my attention span has not been this high in decades. I take on crazy hard shit now I would have never touched in my doom scrolling fugue state years.
Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com
#130I moved all my custom domains to Fastmail five or six years ago and couldn't be happier. My Gmail only exists to catch legacy messages and Google service notifications. I look forward to the day I can completely migrate out of all their products, but some organizations I work with who use Google for various things have made that a slow slog.
Me too. Moving mail to my own domain is one of the best things I've ever done. To anyone considering it: just do it. Doesn't matter what provider you pick, the important thing is to start receiving mail via your own domain as soon as humanly possible. Once mail is going to your own domain, switching is as easy as updating DNS MX records.
I'll third this. A few years ago I set up both a website (cloudflare) and started using Firefox Relay (proxy email addresses, with a mozmail domain).
I did it to make gmail less sticky and control spam[0]. Then last year I switched to fastmail and it was so easy because I just had to point somewhere else.
Even if you keep Gmail I highly suggest people do this as it's helped with spam and gives me more control. Because I have catchall emails I can even make up an email on the spot, with pen and paper only.
[0] every website gets a unique email and a unique password. Think something like hn@foo.mozmail.com or hn@godelski.com (I don't own those domains, don't try to reach me there). Bitwarden even supports FF Relay!