Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

support.google.com

Post reply on HN
Print view View original

131–140 of 147 posts

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#131

Post by nottorp »

dataflow wrote: post #87
nottorp wrote: post #70

Hmm I'm confused. I have my own domain that is totally not hosted on google. However, I use Google's SMTP to send mail as that domain (specifically the one email address that is enabled on my custom domain). For that I'm authenticating to the SMTP with my google account, and I somehow proved to google i own the email a couple billion years ago when we all had pet dinosaurs. Are they discontinuing that or something el…

I'm similarly confused/upset, but it really does sound like they're discontinuing sending via SMTP: > The “Send as” feature will no longer be available. This feature allows you to send email from a third-party address, such as @hotmail.com, @yahoo.com, and others, using your primary Gmail account. https://support.google.com/mail/answer/17101213?sjid=2314716...

Ah well. Google helps me degoogle. Can't complain much can I?

Anyone has recommendations for send-only (or that allow being used only to send) email services? Not those that are used for commercial emails, even if legit.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#132

Post by carlosjobim »

netllama wrote: post #109
anticorporate wrote: post #31

I 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.

How are you dealing with Fastmail's very low storage limits? Or are you paying for more (in which case, this isn't really an equivalent comparison).

They don't have their basic plan anymore. Now it costs $5 instead of $4 and you get 60 GB instead of 5 GB.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#135

Post by downloadram »

armadyl wrote: post #89
evolve2k wrote: post #80

Earlier quoted context omitted.

Proton is activity enshitifying and has introduced dark patterns to their onboarding process. Suggest you deprecate them from your recommend list until they come clean and step away from this dirty business we’ve been seeing. Trust eroding on proton sadly.

Examples?

(not parent) their onboarding pushing is frequent, app is fine but web is popup-y with offers/perks

if i get popups slowing down my web visit it makes me less likely to upsell to, i'd rather a seperate pricing page that i have to manually click to see, my memory serves that most services ive bought have no popup modal (my memory is probably wrong statistically but right emotionally\

maybe op was a/b tested to something more irritating

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#136

Post by armadyl »

downloadram wrote: post #135
armadyl wrote: post #89

Earlier quoted context omitted.

Examples?

(not parent) their onboarding pushing is frequent, app is fine but web is popup-y with offers/perks if i get popups slowing down my web visit it makes me less likely to upsell to, i'd rather a seperate pricing page that i have to manually click to see, my memory serves that most services ive bought have no popup modal (my memory is probably wrong statistically but right emotionally\ maybe op was a/b tested to somethi…

> (not parent) their onboarding pushing is frequent, app is fine but web is popup-y with offers/perks

Fair. They do advertise plans to existing subscribers, even plans that aren’t even an upgrade from your current one.

However on the other hand they do offer a toggle to turn these off completely in the settings. One could argue that it should be opt-in rather than opt-out though.

I wouldn’t count this as a black mark against their reputation though as it’s not the product inherently getting worse.

Funny enough this has been pointed out a lot pretty frequently this past week.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#137

Post by tclancy »

lrvick wrote: post #129
tclancy wrote: post #116

Earlier quoted context omitted.

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 t…

In my face then. You are killing it.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#138

Post by general1465 »

armadyl wrote: post #123
general1465 wrote: post #90

Earlier quoted context omitted.

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…

Yes it is completely ambiguous stupid nonsense especially for emails which when sent anywhere outside of Tuta are not E2EE. How many emails are going to go outside of Tuta service 99%+?

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#139

Post by loloquwowndueo »

netllama wrote: post #110
loloquwowndueo wrote: post #106

> third-party email addresses, such as @yahoo.com or @outlook.com. Unfortunate choice of examples as it doesn’t make it clear whether it applies just to other free web email providers or also to e.g. my own custom domains.

Custom domains are still 3rd party.

There you go, was that so hard to include in the original document?
Post reply on HN