Bonus is that I use a separate subdomain of my custom domain for disposable email addresses which means it never fails email checks (some don't like disposable/temporary email domains).
Bonus is that I use a separate subdomain of my custom domain for disposable email addresses which means it never fails email checks (some don't like disposable/temporary email domains).
The advantage of iCloud is that it's a domain laymen use - those same laymen the "growth & engagement" scum wants to track and spam. They can't just ban it wholesale without alienating a large chunk of their target market (and a pretty lucrative one at that, since Apple hardware is expensive).
There’s only been a handful of times I’ve used it, maybe 12? At least a few of those times it wouldn’t even let me submit it saying it was an “invalid email”. Couldn’t even get past the validation.
I suspect they validate by looking up the MX record and block it based on the entry containing simplelogin.co
A custom domain that only I use specifically for disposable emails would look indistinguishable from any other custom domain out there, and nobody else would have used it for them to even be aware of its existence.
To block it pre-emptively, they’d have to either be omniscient or block every single custom domain in existence. The former I highly doubt is the case, the latter would generally do more harm than good to them.
> humanity will go extinct March 11th, 2401
Please explain! Citation required :) /s
Microsoft, Google, Apple
I do believe Google requires Workspace to have a custom domain, though.
The alternative I currently use is letting Gmail handle the spam. I used to be big into jon-foo@jrock.us for "foo" and that sort of thing, but every address ended up on every spam list anyway, and the filtering didn't increase the signal to noise ratio.
For true throwaways I just use mailinator. If I want to receive email from someone someday, I can just create another account. If they spam me, Google will filter it out. So it goes.