Live data from Hacker News

Reasons to not use your own domain for email

bautista.dev

161–170 of 227 posts

Re: Reasons to not use your own domain for email

#161
post #95

I sometimes wonder if I should set up email with custom domain, but then I read how it will be quickly blacklisted by everyone and your mail simply won't be reaching anyone. That is the biggest problem I think, not the domain payments.

The domain is not the problem. The ip reputation might be.

Use a reputable email hosting service with your domain, problem solved.

Re: Reasons to not use your own domain for email

#162
post #110

I strongly disagree. - Google has on multiple occasions terminated accounts for no reason with no recourse. You loose access you can't do anything. If you have your own domain you can at least set it up somewhere else. How many website would you need to update with your new email and how would you get thay extra factor mail? - If I die I don't care if someone else reads my mail, I'm dead. Also you can add a dead man'…

As evidenced here the impact of account terminations can have a profound impact on a persons life. Email providers like Google should be treated as utilities and regulated as such, they should be legally obligated to communicate with their users, ideally working towards a resolution. Until then you really should be treating said accounts in the same way you would a hotel rental phone.

In my opinion, for the US, the postal service should offer free email addresses to every US resident. The Postal Service is highly regulated, and you won't lose your email over a comment on Youtube.

Re: Reasons to not use your own domain for email

#163

I strongly disagree. - Google has on multiple occasions terminated accounts for no reason with no recourse. You loose access you can't do anything. If you have your own domain you can at least set it up somewhere else. How many website would you need to update with your new email and how would you get thay extra factor mail? - If I die I don't care if someone else reads my mail, I'm dead. Also you can add a dead man'…

Even if there is no option for 100 year registration, 10 years is pretty common[0]. Google deactivates an account and deletes all data after 2 years of inactivity[1]. So even if someone stops using the domain, all data would be deleted after 2 years, emails sent to it would bounce for ~8 years, and only then could someone take ownership of the domain. Even if you're using another paid service, your payments would fai…

... and if you die when your domain has one year left?

Re: Reasons to not use your own domain for email

#164
post #67

I strongly disagree. - Google has on multiple occasions terminated accounts for no reason with no recourse. You loose access you can't do anything. If you have your own domain you can at least set it up somewhere else. How many website would you need to update with your new email and how would you get thay extra factor mail? - If I die I don't care if someone else reads my mail, I'm dead. Also you can add a dead man'…

> Also you can add a dead man's switch This is something I've struggled to find a solution for. Do you have any suggestions? The best I've come up with is a safe with enough information to provide access to my password manager, but obviously this makes me pretty uncomfortable. I could hand it over to a lawyer as part of my will, maybe?

Avoid Liberty Safes when selecting your safe.

https://www.locksmithledger.com/safes/news/53071785/liberty-...

Re: Reasons to not use your own domain for email

#165
post #75

Earlier quoted context omitted.

I co-founded a vanity e-mail provider around 2000, and we 1) registered about 60,000 domains that we provided e-mail for, and we never had problems like that despite tens of thousands of those domains being with then-obscure ccTLDs, 2) a bit later launched the .name top-level domain, and for that we had some very limited initial teething problems because people back then still stupidly used regexes that assumed tld's…

> With respect to saying it out loud, I occasionally have to repeat my e-mail address once, but that's usually all it takes; we must be dealing with very different people. It's not so much having to repeat myself - it's just me@myname.com - but people who apparently have never encountered an address that isn't @gmail.com etc before, who then want to have a 10 minute Q&A/tutorial session where I explain to them how do…

> but people who apparently have never encountered an address that isn't @gmail.com etc before

I've just never had that occur in the 30 years I've used e-mail, and it seems absolutely bizarre given that most people deal with e-mails from schools, or workplaces, or all kinds of other providers all the time.

I get the occasional question of how I got .com, and that's it.

Re: Reasons to not use your own domain for email

#166
post #126

Earlier quoted context omitted.

There's little need to nationalize, since emails don't have a last-mile or natural monopoly issue. I think, however, that modern countries should provide all citizens with an official, public, mail address. Restrict them to only send/receive emails to/from a whitelist of publicly registered service providers with very strict personal data governance requirements (government, banks, utilities, medical services, higher…

Estonia tried this with national first.last@eesti.ee email for everyone. Turns out nobody cared and they will shut it down on 1. November. https://news.err.ee/1608966110/ria-ends-support-for-eesti-ee...

Doesn’t seem to be the same thing:

> The addresses that appear as firstname.lastname@eesti.ee (for example, mariann.mustikamets@eesti.ee) or companyname@eesti.ee (worldsbestransport@eesti.ee) can be used for private correspondence, while it is not part of the public mailbox service. Emails sent to these addresses are not saved in the person's public mailbox but are forwarded to the personal email address they've specified in the Eesti.ee portal (Gmail, Hotmail etc. accounts).

And:

> The decision does not concern people's official personalcode@eesti.ee addresses that can only be used by state agencies.

The latter, which was not discontinued, seems to be closer to what your parent comment was suggesting.

Re: Reasons to not use your own domain for email

#167

The best reason against it is the fact many website, because of stupid policies or incompetent engineers, will reject the address as invalid. Happens to me regularly and makes my life difficult. I still like better than the alternative though. I got locked out of google accounts twice in my life and had one other email provider close entirely.

I’ve had a .me tld for 5 years and am yet to come across a single site that rejects it.

Re: Reasons to not use your own domain for email

#168
post #163

Earlier quoted context omitted.

Even if there is no option for 100 year registration, 10 years is pretty common[0]. Google deactivates an account and deletes all data after 2 years of inactivity[1]. So even if someone stops using the domain, all data would be deleted after 2 years, emails sent to it would bounce for ~8 years, and only then could someone take ownership of the domain. Even if you're using another paid service, your payments would fai…

... and if you die when your domain has one year left?

10 years is just the maximum time a domain can be registered at a given time. You can keep adding a year for every year that passes if you'd like.

Re: Reasons to not use your own domain for email

#170
post #116

Earlier quoted context omitted.

Would you be open to the nationalization of email services? Curious if your very HN-friendly sentiment also implies agreement with this very HN-unfriendly extension.

Given: 1) How critical email is; and 2) Existing mandate of government postal services to guarantee delivery of physical mail to all citizens; that Government postal services should run a national email service free to all citizens. In the USA, email would be minimally covered by the same protective laws as physical mail (I don't know if the same protections are available in other countries). IMAP and POP or a more a…

100MB for storage or per email? For storage, that is way too small. You can easily hit that limit in a few months of light usage. All my utilities send me PDFs each month, and that adds up quickly.

Last year, while doing renovations, the contractor and I were sending PDF drawings back and forth. I would have gone over the limit on a single day.

We need something that lasts a lifetime with full archival and backup.

Post reply on HN