This is a huge selling point. Private email relays often get blocked, the only lasting solution is to put them on the same domain as, and in the same format as, a significant number of non-private email addresses. As far as I’m aware the only other provider doing this is Fastmail.

Comments about lock-in aren’t wrong, but it has to be this way. You can make arbitrary email addresses at your own domain, but anybody who feels like it can trivially automatically detect that those are all you.

Personally I use unique at own domain only where I’m identifying myself anyway, like my bank, and Fastmail masked email where I’m not. For most things it’s not actually that terrible to accept a small risk that they’re offline for a day between your being booted without warning and you changing your email address with them.

▲

glenngillen 2 hours ago | parent | next [-]

Totally agree with unique at own domain isn't actually privacy. It wouldn't take much of a paper trail to work out the details.

I continue to use it everywhere for a few reasons:

- if someone emails me acting all friendly like we've had some previous relationship but it's sent to linked@mydomain or github@mydomain I know they've just scraped my contact details and it's spam

- similarly, if a vendor leaks or sells my data and I start receiving marketing from somewhere I don't expect it's easier to trace the source of the leak (and in some cases just blackhole that entire email address)

- I already use a password manager and have different passwords on every site, but having a different email address too raises the barrier further for someone trying to script an automated attack based off some other pwned data set.

	▲	kqp an hour ago \| parent [-]
		I agree with all of this. I’d add that it’s useful for sorting and searching. Things like keyword matching, from address, and from domain aren’t as consistent as you’d hope, but companies do need to actually email the address they were given, so you can use it to reliably identify emails from them.

▲

riddlemethat an hour ago | parent | prev | next [-]

I configured about a dozen domains to have MX records for the mailinator disposable inbox service for about a decade for free as a gift and the domains were toxic for any other email use case for years afterwards… they were so abused you couldn’t even sign up for most web services with any email associated by the time I stopped renewing them… there are still GitHub lists of disposable email addresses that list to blacklist those domains (and many other), so, I agree. If the big providers don’t offer disposable email addresses there is no good option.

	▲	nunez 41 minutes ago \| parent [-]
		Mailinator was an awesome service when it first worked. Thank you!!!

▲

8cvor6j844qw_d6 2 hours ago | parent | prev [-]

> This is a huge selling point.

Same thoughts. I'm annoyed with the number of services that blocks alias domains.

At least I don't see services attempting to block @icloud.com domains.