3 ms·
> Long story short: now both Sign in with Apple and Hide My Email aliases are going to be issued on the @private.icloud.com subdomain. This makes it much easier
by mortenjorck 4mo ago
> Long story short: now both Sign in with Apple and Hide My Email aliases are going to be issued on the @private.icloud.com subdomain. This makes it much easier to ban all aliases without affecting non-relay mailboxes on iCloud mail.
Could someone clarify why having Sign in with Apple and Hide My Email on the same domain would make a blanket ban easier rather than harder? What am I missing?
- BoorishBears 4mo agoI guess their thought process is, both alias and non-alias accounts use @icloud.com You were always able to reserve a normal icloud email address just like you would a GMail account, so banning all icloud email addresses would be banning non-alias Apple customers That being said, I'm not convinced anyone who wanted to ban aliases couldn't have already. The alias emails look weird enough I'm guessing you could ban them with few false positives.
- SXX 4mo ago> The alias emails look weird enough I'm guessing you could ban them with few false positives. While this is true not all of them been weird. Some can be just word + number + word without dots or underscores. Also blanket banning whole domains is just much easier and already done for temporary emails. No false positives.
- BoorishBears 4mo agoThe point of the article is previously banning Apple's temp domain would create many false positives (all the normal Apple registered emails that chose @icloud.com during setup)
- w10-1 4mo agoBefore, the emails were "me@icloud.com", the default for all apple users. There was no way to distinguish normal emails from generated private emails. Now, they will be "blah@private.icloud.com", so it will be easy to ban the generated/private email that reduces the ability to associate logins across services. Unclear why Apple would shoot themselves in this way; I hope it's not Ternus complying with anti-privacy.
- utilize1808 4mo agomaybe to avoid getting their legitimate email servers banned by other servers since they host (i.e. being exploited) a growing number of spam accounts.
- SXX 4mo agoYou cant send mail from Hide My Email aliases. They are only work one way.
- nielsbot 4mo agoYou can send from Hide My Email addresses: https://support.apple.com/guide/icloud/use-hide-my-email-in-mail-mmca4d729d79/icloud#mm2ee7ee328e https://support.apple.com/guide/icloud/use-hide-my-email-in-... I think I've also seen this in Mail.app but that's not shown on this page.
- SXX 4mo agoWow my bad I wasnt aware its possible. I remember someone in HN comments complaining about it being one way only back in 2024. UPD: apperently this supposedly only work if someone message you first. So you still cant spam from aliases.
- nielsbot 4mo agoOk thanks. Directions are misleading then.
- int_19h 4mo agoFor most online businesses, blocking Apple email servers sounds like a good way to kill off the portion of your customer base that has the most money to spend.
- reaperducer 4mo agoNow, they will be "blah@private.icloud.com" I've been in the ecosystem long enough to have .iCloud.com, .me, .mobileme.com, iTunes.com, and probably one or two more addresses all assigned by various Apple services over the years before they started unifying the systems. They all work, and independently of one another. I wonder if all the domains will be migrated, and how namespace collisions will be handled.
- gobip 4mo agoApple was generating (something)@icloud.com whenever you used that service. Now, it will use (something)@private.icloud.com instead. So you can ban this subdomain instantly, knowing people will be "hiding" with this service by default. It's like blocking anondaddy, simplelogin etc but not protonmail.