Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Ooooooh. I thought this was a completely different thing in my mind.
I was thinking that Apple would also be responsible for registering the domain users wanted and setting it all up as part of the iCloud subscription.
I was really wrong on this one 😅
 
It's surprising how many people don't understand custom domain email hosting. Do you own your own domain name and need a place to host email that isn't Google Apps, Microsoft 365 or a personal server? Then this iCloud+ feature is for you.

This is certainly not a feature for everyone and it's actually a fairly "advanced" consumer feature by Apple standards

I have my own domain and email hosted elsewhere for it, and this new functionality has really confused me. I get it now that people are technically explaining it, but for a while there was no information, and I knew too much about how domain and email hosting works to figure out what Apple meant with their early announcements. I still don't know why I'd ever use it - I guess to save money because I wouldn't need to my email elsewhere and I'm already paying for iCloud+.
 
  • Like
Reactions: DotCom2
I successfully got it working with one of my domains--I am very familiar with MX records and DKIM and such.

But: My other main domain mostly works, but I cannot add the one email address I need to add! It, and only it, gives me a "Couldn't verify your email" error.

Very frustrating!

It may be because the email address in question used to be my iCloud username before I switched my iCloud username to just be an iCloud email address.

ps: I agree the instructions are likely to be very confusing for people not used to DNS records, and they are incorrectly worded at one point--telling people to "copy exactly" some text, when in reality you need to put different text into different fields in the CName record, and not copy the part of the text that tells you what field to put it in. Unless other registrars have a different interface than Namecheap.
 
I'm so confused. I own a specific domain, I already have email addresses on this domain setup to forward to my gmail accounts. How is this any different?
I do the same exact thing. It’s not practically different. Instead of you forwarding emails, iCloud+ will actually host the sending and receiving of emails to and from your email attached to your custom domain.

If all you are doing is forwarding to your gmail, you would benefit from this, because right now if you reply to any of those emails, you will be sending the email from your gmail. If you set this up (properly), you can actually reply from your email@customdomain.com email address. You’ll look all professional! 😎
 
If I was a betting man, I would put a few quid on Apple exploring iApps for business.

Both Microsoft and Google have their offerings with Google Apps and Office 365. Both offer collaboration features in their suites and full integration with E-mail and messengers.

Apple has a lot of pieces of the jigsaw already in place. The iWork apps. Real-time collaboration. Messages. FaceTime. From a business perspective, it’s lacking the integrated wraparound, administration elements and business tailored email at the moment.

I wouldn’t be surprised in the slightest if this isn’t a way of “trialling” one of the features that would be required to start on-boarding businesses by using “less important” personal users.

For small to medium size businesses that primarily use Apple devices, it would make a lot of sense for them not to have to rely on Google Apps or Office 365 and instead use Apple services.
 
I'm so confused. I own a specific domain, I already have email addresses on this domain setup to forward to my gmail accounts. How is this any different?
Functionally not very different for you as a user. The difference really is you're not forwarding the email from your own domain to anyone else. When someone sends you an email, behind the scenes, it looks up that address, and routes it to Apple's email servers directly. You then use your Mail client directly with Apple's servers hosting the data for that email account. When you send mail, it sends directly from that account. With your current-state forwarding example, that inbound email looks up the address, sends it to wherever your domain is registered, who then forwards it to a separate account at gmail (with it's own separate email address). Reply's then usually would come from the separate gmail account.
 
I successfully got it working with one of my domains--I am very familiar with MX records and DKIM and such.

But: My other main domain mostly works, but I cannot add the one email address I need to add! It, and only it, gives me a "Couldn't verify your email" error.

Very frustrating!

It may be because the email address in question used to be my iCloud username before I switched my iCloud username to just be an iCloud email address.

ps: I agree the instructions are likely to be very confusing for people not used to DNS records, and they are incorrectly worded at one point--telling people to "copy exactly" some text, when in reality you need to put different text into different fields in the CName record, and not copy the part of the text that tells you what field to put it in. Unless other registrars have a different interface than Namecheap.
Agree, some of the record entries are not copy and paste. You need to understand your DNS hosting platform and how entries are put in so you get it right.
 
Hmm, so your accounts are now hosted on Apple's machines. That'll save me a bit of hosting $$. Is there a limit to the # of domains you can host?
 
I'm so confused. I own a specific domain, I already have email addresses on this domain setup to forward to my gmail accounts. How is this any different?
The point of custom domains not forwarding, but to make it so that you send emails canonically "from" your domain. Not, by the way, as an alias--Google allows you to send "from" alternate domains, but that is not the same--these are often just aliases, emails sent in this way are much more likely to be flagged as phishing or spam. You need to change your DNS records to verify what email servers you're going to use.

With forwarding, you get an email to one service and then, obviously, it forwards to another. With proper custom domain support, you just use the one email service and your email is not forwarded.
 
Tried setting this up and all going well until the verification email - tried a number of times and still not received. (Other mail to the domain is being delivered okay).

Anyone else seeing this delay?
 
Similar. I have a single catch-all. Every site I sign up for, I use sitename@mydomain.com.

If I start receiving spam or other unsolicited mail to a particular address, I know which website leaked my details and can nix the address without having to update my email details at any other websites.
Never used a wildcard before, but just set it up and removed a few aliases because of it. Thanks for the tip!
 
Like many, I don’t see the value in this… or most probably I don’t understand the feature.
i don’t own a domain name, so I can’t use this feature. Right?
if I owned one, I would have access to email addresses with my domain name, right?
If I owned a domain email, I could have/would have used it as my AppleID. Right?
If I owned multiple domain emails, I could have configured them in Apple Mail. Right?
So what does this do?
Owning a domain just means you own a domain. It does not include email necessarily--just the ability to add information about what email you use. Many registrars do provide email, maybe as an add-on, and most include a minimal email setup that lets you set up forwarding address. In any event, the MX records in your DNS for the domain specify what email service you're going to use.
 
Similar. I have a single catch-all. Every site I sign up for, I use sitename@mydomain.com.

If I start receiving spam or other unsolicited mail to a particular address, I know which website leaked my details and can nix the address without having to update my email details at any other websites.
i do the same. it's a must have feature for me.
 
  • Like
Reactions: BillyBobBongo
I successfully got it working with one of my domains--I am very familiar with MX records and DKIM and such.

But: My other main domain mostly works, but I cannot add the one email address I need to add! It, and only it, gives me a "Couldn't verify your email" error.

Very frustrating!

It may be because the email address in question used to be my iCloud username before I switched my iCloud username to just be an iCloud email address.

ps: I agree the instructions are likely to be very confusing for people not used to DNS records, and they are incorrectly worded at one point--telling people to "copy exactly" some text, when in reality you need to put different text into different fields in the CName record, and not copy the part of the text that tells you what field to put it in. Unless other registrars have a different interface than Namecheap.
I have 3 email accounts in Fastmail with my domain, iCloud wouldn't let me set up one so guessing it's because my son uses it for his iCloud / Apple ID.
 
I do the same exact thing. It’s not practically different. Instead of you forwarding emails, iCloud+ will actually host the sending and receiving of emails to and from your email attached to your custom domain.

If all you are doing is forwarding to your gmail, you would benefit from this, because right now if you reply to any of those emails, you will be sending the email from your gmail. If you set this up (properly), you can actually reply from your email@customdomain.com email address. You’ll look all professional! 😎
Just a word of warning: Gmail does allow you to send from aliases. Those are very different--you're not really sending "from" your custom email address, but still from Gmail, and Gmail recipients will even see "from blah@gmail on behalf of blah@custom" or something. Apple is doing this the right way! (Though I am annoyed that I can't add my email address for unrelated reasons.). It's just that the right way is complicated. the right way also looks more professional to recipients and is less likely to get your emails flagged as spam or phishing.
 
It isn't necessarily solving a problem but adds more features to make iCloud compelling. I have used Google Workspace, called something quite different when I signed up in 2008, for hosting my custom domain email. I like owning my own personalized address that I can move from provider to provider or, as I have in the past, host my own email server. Sure, it is niche, but Office 365, Google, and others already do it so now iCloud is having some feature parity.
are you planning on moving from GWS to icloud? I'm thinking about it.
 
I have 3 email accounts in Fastmail with my domain, iCloud wouldn't let me set up one so guessing it's because my son uses it for his iCloud / Apple ID.
Does it let you add it at all, and then it fails the verification?

At first, I couldn't even add it. Now it fails verification. Not sure if a change to my DNS caused that (seems unlikely) or it's because I removed the email as an alternate contact method. It still doesn't work either way.
 

Attachments

  • Screen Shot 2021-08-25 at 10.56.10 AM.png
    Screen Shot 2021-08-25 at 10.56.10 AM.png
    158.3 KB · Views: 70
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.