Live data from Hacker News

iCloud+ custom email domains should be better

domlaut.com

41–50 of 145 posts

Re: iCloud+ custom email domains should be better

#42

I don't know why anyone would use a catch-all these days, unless you want to get inundated with spam.

I use a catch-all for my email and give business unique emails. I don't have a spam issue, at least not for any emails except for the "main" email.

Re: iCloud+ custom email domains should be better

#43
post #37

Catch-all addresses are a must have for me now. I allocate unique addresses to every website as these are more robust then using the + operator because they can't be stripped off. I've already busted one company (I presume selling) my email address to a cloud provider for them to send me marketing material. I emailed their privacy officer and didn't even get a reply, but that's OK, if it continues, one sieve rule and…

Why not use iCloud’s private email feature to generate a new email that forwards to your regular email for these purposes?

Re: iCloud+ custom email domains should be better

#44

I'm optimistic that Apple is working on most of these issues (especially catch-all) right now and this is just representative of their new offering. Like many things I've seen from Apple it will take a release cycle or two (of 1-2 years per cycle) to bring in this arguably basic functionality - as is tradition we'll groan about other issues being held back in favour of fancy new features. I have no doubt they intend…

I would fear that Apple forgets about the feature after a few years and then just drops it. This is not central to their business and Apple trims such things very agressively. I would always buy a domain-email from somebody who has this as their main business, and I would never couple my email to Apple which could lock me out of my account if they think I "behave suspiciously".

On the contrary, services are where Apple has been spending a lot of focus, for better or for worse.

Re: iCloud+ custom email domains should be better

#45

I'm optimistic that Apple is working on most of these issues (especially catch-all) right now and this is just representative of their new offering. Like many things I've seen from Apple it will take a release cycle or two (of 1-2 years per cycle) to bring in this arguably basic functionality - as is tradition we'll groan about other issues being held back in favour of fancy new features. I have no doubt they intend…

I would fear that Apple forgets about the feature after a few years and then just drops it. This is not central to their business and Apple trims such things very agressively. I would always buy a domain-email from somebody who has this as their main business, and I would never couple my email to Apple which could lock me out of my account if they think I "behave suspiciously".

> I would fear that Apple forgets about the feature after a few years and then just drops it.

This is a Google thing to do. Apple seems pretty great at picking and choosing commitments before they launch rather than what you describe here.

Re: iCloud+ custom email domains should be better

#46

I'm surprised Apple supports custom email domains to any extent. Apple is a consumer electronics company. Hosted email on custom domains is very distinctly not a typical consumer behavior.

Services is a big growth area for them and it lets them beef up their iCloud+ offering

Re: iCloud+ custom email domains should be better

#47
post #43
post #37

Catch-all addresses are a must have for me now. I allocate unique addresses to every website as these are more robust then using the + operator because they can't be stripped off. I've already busted one company (I presume selling) my email address to a cloud provider for them to send me marketing material. I emailed their privacy officer and didn't even get a reply, but that's OK, if it continues, one sieve rule and…

Why not use iCloud’s private email feature to generate a new email that forwards to your regular email for these purposes?

Just my personal opinion, but the reason I got a domain to start with was to not be dependent on a specific provider.

Also, it's is far nicer to be able to simply sign up to a website with company@example.com than go generate a random email. Especially if you are on another device.

Re: iCloud+ custom email domains should be better

#48
Bad error messages is kind of an institutional problem at Apple. Somehow there’s a push to “simplify” the error process and it invariably means that some part of e pipeline has good error info that is, if you’re lucky, dropped in a log somewhere and just completely swallowed if you’re not. In the UI you’ll just get a generic “something went wrong” or a “translated” error that isn’t bijective at all, or sometimes not even an indication that something went wrong (particularly around ambient operations like syncing). It’s really quite frustrating how often I need to go through a truly awful amount of spelunking just to figure out what a “user friendly” message means, which is pretty much the opposite of user friendliness.

Re: iCloud+ custom email domains should be better

#49
post #43
post #37

Catch-all addresses are a must have for me now. I allocate unique addresses to every website as these are more robust then using the + operator because they can't be stripped off. I've already busted one company (I presume selling) my email address to a cloud provider for them to send me marketing material. I emailed their privacy officer and didn't even get a reply, but that's OK, if it continues, one sieve rule and…

Why not use iCloud’s private email feature to generate a new email that forwards to your regular email for these purposes?

[deleted]

Re: iCloud+ custom email domains should be better

#50
Like many, I got bit by the end of legacy free Google Workspace so I've been figuring out my options.

One related issue is how to get email off of Google Workspace. After checking out various options, I've settled on using imapsync (https://github.com/imapsync/imapsync).

Unfortunately, the official Docker image was throwing errors for me while trying to move an almost 100k email account. Ended up building a modified version which I have now been able to successfully use to migrate. Image: https://hub.docker.com/r/jauderho/imapsync Dockerfile: https://github.com/jauderho/dockerfiles/blob/main/imapsync/D...

HTH.

Protip for those moving to iCloud+ custom email domains, you HAVE to temporarily set the SPF record to exactly match what Apple wants to see during the initial setup. Else it will complain that setup cannot be completed. You can revert it to whatever you had it set to previously (plus include:icloud.com) once the setup is complete.

Post reply on HN