Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Is it just me, or have references to this feature gone missing from Apple's pages?
Nope, it’s still there… it’s on the more detailed “Features” page…


Apple never made a big deal about it. That came from folks like us who happened across that one obscure reference to it — which to be fair is the only thing we actually know about it. Everything else is just speculation. Educated speculation, to be fair — email systems have to work a certain way — but still entirely guessing based on the limited ways in which Apple would have to implement it.
 
Nope, it’s still there… it’s on the more detailed “Features” page…


Apple never made a big deal about it. That came from folks like us who happened across that one obscure reference to it — which to be fair is the only thing we actually know about it. Everything else is just speculation. Educated speculation, to be fair — email systems have to work a certain way — but still entirely guessing based on the limited ways in which Apple would have to implement it.
Ah thanks. I just hope they launch it before the actual iOS/iPadOS launch as this is not tied to the OS in any way. The mail client on all their OSes supports alias-es already, this would be just another alias.
 
Not a feature for me, I have my own email servers and multiple email addresses. I think if you find it will only work with Apple mail and the email addresses will still resolve to @icloud.com. You can't just make your own domain name and expect it resolve through conventional name servers.
 
Hopefully this'll be available soon for further testing. Would like to know the real integration; hopefully this is not exclusively limited to a single domain registry like GoDaddy with Outlook.
 
Last edited:
I later found that Apple's spam filtering system would 'score' each e-mail as spam (as shown in the headers) but would then still deliver it to my Inbox, despite having Junk Mail filtering turned on. Many of the servers sending spam were on blacklists but, again, Apple accepted mail from them. I even had several converations with people in Cupertino about it but with no real resolution.
Glad to know I'm not alone. I spent 6 years sending emails to Tim Cook and Eddy Cue about this issue before finally giving up. They use Proofpoint for their spam filtering and it sucks. Apple Mail's own bayesian filter could do a better job at filtering out egregious spam. I don't know why it's not a priority for them to fix this. I even emailed Woz to find out if he had any pull up there anymore:
I don’t have any direct pull.

But I agree with you totally that this is an APPLE fail.

Spam is a violation of our privacy. This should mean something to Apple.

best,
Woz
 
Glad to know I'm not alone. I spent 6 years sending emails to Tim Cook and Eddy Cue about this issue before finally giving up. They use Proofpoint for their spam filtering and it sucks. Apple Mail's own bayesian filter could do a better job at filtering out egregious spam. I don't know why it's not a priority for them to fix this. I even emailed Woz to find out if he had any pull up there anymore:
It really is an Apple FAIL. What is strange to me is that SPAM does not go through in Apple Mail on my Mac but does go through on iOS. It really is frustrating to see the red circle dot over and over and over again even though I have it set to send straight to Trash.
 
It really is an Apple FAIL. What is strange to me is that SPAM does not go through in Apple Mail on my Mac but does go through on iOS. It really is frustrating to see the red circle dot over and over and over again even though I have it set to send straight to Trash.
That's because Apple Mail on the Mac has its own spam filters. iOS Mail doesn't.

In theory, if the Mail app is actually running on your Mac, it should still process the inbound spam and follow your rules accordingly, but that won't sync up right away with an iCloud account, since it only supports push notifications for new messages; deletions and moves don't get updated until the next time you either manually refresh the app, or another new email message comes in.

Basically, iCloud Mail's push notifications are as broken as its spam filters are. FWIW, this is why I use Fastmail. It manages to get both right.

Alternatively, you can set your iCloud Mail account to "Fetch" instead of push, in which case it will at least update every 15 minutes, but you'll lose immediate notifications for new email messages — they'll also only come in at the normal 15-minute fetch intervals.
 
  • Like
Reactions: DotCom2
We're now into August and still nothing about that custom domain... I wouldn't be surprised if it's not even being enabled AFTER the official release of iOS15
 
We're now into August and still nothing about that custom domain... I wouldn't be surprised if it's not even being enabled AFTER the official release of iOS15
Yep, just imagine about AirPlate fail... And I think the whole process of integrating new domains, customer frontends for further configuration etc. should be tested to not be buggy on release. So I'm not quite sure if this feature will be what we dream about...
 
  • Like
Reactions: bob24
I think the whole process of integrating new domains, customer frontends for further configuration etc. should be tested to not be buggy on release. So I'm not quite sure if this feature will be what we dream about...

100% agree. I doubt full support for custom emails with MX settings and the likes would be deployed in production alongside iOS 15 without some sort of public beta beforehand; so I am starting to wonder what to expect.
 
100% agree. I doubt full support for custom emails with MX settings and the likes would be deployed in production alongside iOS 15 without some sort of public beta beforehand; so I am starting to wonder what to expect.
To be honest, it's not nearly as complicated as it sounds on the back-end. Once you're already running a mail server, adding support for additional domains is actually pretty trivial in principle. I have no idea what Apple is using on the back-end, but it can't be more complicated than any other mail server. Even on Apple's own Mac OS X Server, which runs the open-source dovecot and postfix under the hood, I can add in support for another domain name in about 30 seconds. It's really just a config file entry.

If all Apple plans to do is let tech-savvy users setup their own MX records and then receive email for other domains, that's actually really simple. However, knowing Apple, it wants to build a more turnkey solution, which means the real work will be in building the user interface for it. The fact that the beta iCloud Mail web interface doesn't even have rules implemented yet isn't promising.

I don't expect it's going to need a public beta per se, although Apple may take the same approach it's done in the past and call the whole thing "beta" for the first few months just to manage expectations, much like we saw with iCloud Photo Library and the web versions of iWork.

Personally, I wouldn't be surprised if this is held off until later this year. On the iOS 15 Features Page, which is the only place that any evidence of Custom Email Domains even exists, there's actually an asterisk beside "Hide My Email" that says "Coming in a software update later this year." However, since Hide My Email has already been working just fine in the iOS 15 betas—and even on the iCloud web interface—for well over a month now, I've suspected for a while that Apple put the asterisk in the wrong place there, and it's Custom Email Domains that are actually coming later.
 
  • Love
Reactions: DotCom2
To be honest, it's not nearly as complicated as it sounds on the back-end. Once you're already running a mail server, adding support for additional domains is actually pretty trivial in principle. I have no idea what Apple is using on the back-end, but it can't be more complicated than any other mail server. Even on Apple's own Mac OS X Server, which runs the open-source dovecot and postfix under the hood, I can add in support for another domain name in about 30 seconds. It's really just a config file entry.

If all Apple plans to do is let tech-savvy users setup their own MX records and then receive email for other domains, that's actually really simple. However, knowing Apple, it wants to build a more turnkey solution, which means the real work will be in building the user interface for it. The fact that the beta iCloud Mail web interface doesn't even have rules implemented yet isn't promising.

I don't expect it's going to need a public beta per se, although Apple may take the same approach it's done in the past and call the whole thing "beta" for the first few months just to manage expectations, much like we saw with iCloud Photo Library and the web versions of iWork.

Personally, I wouldn't be surprised if this is held off until later this year. On the iOS 15 Features Page, which is the only place that any evidence of Custom Email Domains even exists, there's actually an asterisk beside "Hide My Email" that says "Coming in a software update later this year." However, since Hide My Email has already been working just fine in the iOS 15 betas—and even on the iCloud web interface—for well over a month now, I've suspected for a while that Apple put the asterisk in the wrong place there, and it's Custom Email Domains that are actually coming later.

It is still going to be complicated for most regular users. For the average user, it is more than just adding an MX record. That is the the easiest part.

First, most users do not own their own domain. So, is Apple going to be a domain registar or are they going to partner with someone?

What if user wants a domain that is personal to them? How are they going to react when their domain is not avaliable.

What about DNS services? If Apple is partnering, the registar can handle. Do most users even understand DNS?

Is Apple going to offer some form of Autoconfig (like I can do with Exchange/Exchange365) or do users need to manually setup their email settings?

I tend to agree that I don’t see this being released in the fall. Since all we know about it is that Apple is going to introduce something, the devil is still in the details.
 
It is still going to be complicated for most regular users. For the average user, it is more than just adding an MX record. That is the the easiest part.
Yup, and that's kind of my point about the UI. From a back-end technical perspective, it's not difficult at all. Doing it "the Apple way" is another story entirely, of course, and that's where the UI side of things comes in. That doesn't really require testing, however — once Apple has everything ready, it will just work. It's getting it ready that's the trickier part.

The scope of this isn't really that large, as it's clearly intended to be pretty basic, but that makes it all the more important that Apple make it as simple as possible for the average user to set up.

First, most users do not own their own domain. So, is Apple going to be a domain registar or are they going to partner with someone?
I think it's been discussed elsewhere in this thread (or another similar one here on the MR forums), but I've become convinced that Apple isn't going to become a domain registrar. That's an extremely complicated thing for Apple to do just to provide custom email addresses for families — unless of course Apple only plans to only give out ".apple" custom domain names 😏

The most likely solution is that Apple will partner with someone. It's hard to say what form that will take, but I'm hoping it's a more generic partnership, as opposed to something that requires users to work with a specific registrar, the way Microsoft did with GoDaddy.

What if user wants a domain that is personal to them? How are they going to react when their domain is not avaliable.
I'm not sure Apple cares too much about that. What do folks do when they want a Gmail or iCloud address and it's not available? Or a vanity license plate for that mater? I don't think that's going to be a difficult concept for most people to grasp.

What about DNS services? If Apple is partnering, the registar can handle. Do most users even understand DNS?
Yup, again, this is why I think a turnkey solution is going to be required. I doubt Apple will provide DNS services for this purpose — again, that's overkill just to offer custom email addresses.

My guess — and it's just a guess — is that there will be a "one-button" solution at some big DNS provider. However, this may not even need to be a special partnership with Apple, per se. Many DNS providers already offer pre-configuration APIs that Apple can simply plug into. Google has been doing this for years with G Suite / Google Workspace.

Is Apple going to offer some form of Autoconfig (like I can do with Exchange/Exchange365) or do users need to manually setup their email settings?
Well, that doesn't change at all from how iCloud works right now. This isn't about running a custom email server. In fact, since the whole thing will be tied to your Apple ID, it's likely just going to use the exact same iCloud configuration that's already present in iOS and macOS.

Apple's description of the feature is "Personalize your iCloud Mail address with a custom domain name," so it's going to be more like adding an alias to your iCloud Mail than setting up a whole new mail account. The basic UI is already there for this, in fact — the aliases section in the iCloud web preferences is already named "Accounts," and it's not hard to see how it could easily be expanded to handle non-iCloud.com aliases.

I tend to agree that I don’t see this being released in the fall. Since all we know about it is that Apple is going to introduce something, the devil is still in the details.
Yup, and my gut feeling is that this is going to be considerably less exciting than many folks are hoping. It's still targeted as a feature for families, and not for businesses, so you'll still be limited to six accounts, and there may also still be a limit on the number of aliases. I also wouldn't be surprised if it's limited to a single custom domain.

In fact, now that I think about it some more, it's not entirely inconceivable that Apple might consider "a custom domain name" to be only those from a specific TLD that it offers. The description doesn't say "Personalize your iCloud Mail address with your own domain name" but rather with "a custom domain name." Apple registered the ".Apple" TLD years ago, but it's never actually used it for anything.
 
set up web hosting using that domain name
Just to clarify on this, no need to set up web hosting. You can certainly have a domain name that's used for email only, but it's uncommon. As long as the MX DNS records are pointed to the correct server(s), it doesn't care whether there's a website there or not.
 
  • Like
Reactions: jhollington
To be honest, it's not nearly as complicated as it sounds on the back-end. Once you're already running a mail server, adding support for additional domains is actually pretty trivial in principle. I have no idea what Apple is using on the back-end, but it can't be more complicated than any other mail server. Even on Apple's own Mac OS X Server, which runs the open-source dovecot and postfix under the hood, I can add in support for another domain name in about 30 seconds. It's really just a config file entry.

If all Apple plans to do is let tech-savvy users setup their own MX records and then receive email for other domains, that's actually really simple. However, knowing Apple, it wants to build a more turnkey solution, which means the real work will be in building the user interface for it. The fact that the beta iCloud Mail web interface doesn't even have rules implemented yet isn't promising.

Agree the technical aspect isn’t that complicated if you are dealing with users who know what they are doing.

But still it needs to be tested before being called a live feature I think. Firstly to make sure the UI to set this up is working as intended and not confusing users. And secondly (more importantly) to catch as many technical glitches or edge cases as possible which might cause emails to be lost (it really would look bad to have headlines saying the iCloud is dropping emails fro some users).

Then there is what @TriBruin mentioned about less technical customers (if they are left on the sideline it is fine, but if there is some kind of technical integration with a DNS hosting partner and auto-setup, this probably needs to be tested as well).

It really comes down to exactly what this feature will be, but I think it is looking less and less likely they we will get a full-fledge custom domain service launching in production alongside iOS 15.

Even though it would make their wording a bit missleading, one possibility still is that all they mean to say is that they will allow us to setup aliases for our custom domain address on the iCloud website. In that case agree that there isn’t much testing required (that feature existed years ago and was removed).
 
Last edited:
Agree the technical aspect isn’t that complicated if you are dealing with users who know what they are doing.
The technical aspect isn't complicated on the back-end at all. The real trick is going to be building a really simple solution that any iCloud user can take advantage of. This is why I originally wondered if Apple might go so far as to get into the DNS hosting game, but that's extremely unlikely for all the reasons that others have pointed out. I definitely can't see Apple relying on users to figure out how to set this up for themselves. In fact, part of me suspects Apple won't even give more tech-savvy users the option.

That's actually why the possibility also suddenly occurred to me in the post above that Apple might not allow for just any domain to be used. It could simply issue "custom email domains" under a TLD or other domain that it already owns. That would be the most turnkey solution by far, and it wouldn't be a big deal for Apple to provide basic DNS services in that case either, since users wouldn't be using those domains for anything else.

If that turned out to be the case, it would obviously be a huge disappointment for many, but knowing how Apple rolls with iCloud Mail, it honestly wouldn't surprise me. As with most of its iPhone apps, Apple is happy to provide just the basics and leave power users to find better solutions elsewhere.

But still it needs to be tested before being called a live feature I think. Firstly to make sure the UI to set this up is working as intended and confusing users.
You're right that there's a bit of an adoption curve there, but I still think Apple is more likely to slap a "beta" label on the whole thing, like it did with iCloud Photo Library when it first launched. Again, though, that's all UI stuff, and Apple doesn't seem to be overly concerned with what users think of a UI before launching it. Just look at how controversial the changes are in Safari for iOS 15 and macOS 12. The iCloud Mail UI is in the process of being redesigned — you can see it at beta.icloud.com — but it's also clearly still a work in progress.

And secondly (more importantly) to catch as many technical glitch or edge cases as possible which might cause emails to be lost (it really would look bad to have headlines saying the iCloud is dropping emails fro some users).
That would really only require back-end testing, not a public beta. The core email technology we use today has been around for over 40 years, and Apple has even been directly involved in some of the IETF working groups for various internet technologies. If Apple can't figure out how to receive and properly route emails for additional domains, it has no business running a mail server in the first place 😏

iCloud Private Relay and Hide My Email are both more complicated than custom domains, and yet Apple already has those up and running in the iOS 15 betas. That said, the fact that custom email domains are nowhere to be seen yet definitely implies that either it's not launching with iOS 15, or it's not going to be anything like what many of us are expecting.

Then there is what @TriBruin mentioned about less technical customers (if they are left on the sideline it is fine, but if there are some kind of technical integration with a DNS hosting partner and auto-setup, this probably needs to be tested as well).
I don't think Apple will leave anybody on the sidelines, as that's not really Apple's style when it comes to iCloud. In fact, that's arguably the reason iCloud Mail (and related services) have seemed so dumbed-down over the years. Apple prioritizes "simple and accessible" over "powerful and feature-rich."

Again, though, other than the UI, all of the technologies involved in doing this are foundational internet standards and have been well-established for years. I was running multiple domain names on email servers back in 1998, back when one had to submit DNS registrations via email templates. There's no magic to any of this on the back-end, and Apple isn't developing anything new in that regard. Even working with DNS hosting partners has already been done many times. For example, Google Workspace (nee G Suite) has offered a one-button configuration solution for over a dozen major DNS providers for almost a decade now.

The only possible new ground Apple would be breaking here is providing an even more seamless user experience in setting this up. That would be a big deal, and very much an Apple thing to do. That will need to be extensively tested — no IT project manager in their right mind wouldn't put that through testing — but it may not be user-facing testing.

iCloud Private Relay and Hide My Email are more relevant because those UIs are in the actual iOS 15 betas. We don't know if Apple plans for let users configure and manage a custom domain in iOS or macOS directly, beyond the code that already exists for setting up and choosing aliases in the iCloud Mail settings.

It really comes down to exactly what this feature will be, but I think it is looking less and less likely they we will get a full-fledge custom domain service launching in production alongside iOS 15.
Personally, my gut feeling has been that we won't get a "full-fledge custom domain service" launching at all.

Remember that the only thing we know about this right now is one sentence from Apple's iOS 15 Features page:

Personalize your iCloud Mail address with a custom domain name, and invite family members to use the same domain with their iCloud Mail accounts.

This thread (and others like it) are rife with speculation — much of it educated speculation, to be fair, since most of us know how these things work with other providers. We've all been hoping that this will be something akin to what Google Workspace or Fastmail offer, but I after taking a step back and thinking about it, I really suspect it's going to be much less.

Either way, it's important to remember that Apple has nothing about it, and the sentence above doesn't even say "your own domain name" but rather simply "a custom domain name." It's also worth noting the singular use of the word "domain" here.

For all we know, Apple might be planning nothing more than allowing users set up subdomains of iCloud.com for their families (e.g. "john@doe.icloud.com" and "jane@doe.icloud.com"), or even another second-level domain they still control, like me.com.

In fact, the more I think about this, the more I think we're all setting ourselves up for disappointment.

Even though it would make their wording a bit missleading, one possibility still is that all they mean to say is that they will allow us to setup aliases for our custom domain address on the iCloud website. In that case agree that there isn’t much testing required (that feature existed years ago and was removed).
That honestly wouldn't entirely surprise me, but I do think this will be a little bit more than that. I suspect one of the reasons Apple removed that feature years ago was because it really didn't work all that well for the average user, who still needed to have another email account or forwarding service to handle incoming mail. It also created new problems as email validation technologies like SPF and DKIM entered into the mix — this is where there was a real potential for messages to get lost in the sense that they'd be rejected or flagged as spam by the receiving servers.

If Apple goes back to that, it will actually be worse than if they simply left users to figure out how to set up MX records for themselves.
 
Praying to all the lords that multiple custom domains will be part of this, and that it ends up being what most of us think custom domains means 🙃
 
I think and hope “custom domains” means any domain we own. To me, an iCloud subdomain isn’t a custom domain.
 
I think this will result in a interface in cooperation with a DNS registry to have an one click solution (like outlook and GoDaddy).

If that is the case I hope there is an option to keep you own registrar and just setup the required MX entries.

Firstly because if there is a partnership it will probably have an Apple tax attached (i.e. a higher than normal price because Apple wants a cut of the amount paid). And secondly because my domain name is not just used for emails and I want to keep the flexibility to configure DNS entries which are unrelated to email in whichever way I like (if entries are auto-configured as part of a partnership with a registrar, I am not convinced they will leave us complete flexibility).
 
  • Like
Reactions: Roadster Lewis
I just hope that I’d I upgrade my @icloud.com to a custom domain, that it will update it as my primarily Apple ID, because I’m going crazy with having a Gmail and an iCloud email attached. We’re about 6-7 weeks from the release of iOS 15, praying we’ll see something soon.
 
  • Like
Reactions: bob24 and DotCom2
I just hope that I’d I upgrade my @icloud.com to a custom domain, that it will update it as my primarily Apple ID, because I’m going crazy with having a Gmail and an iCloud email attached. We’re about 6-7 weeks from the release of iOS 15, praying we’ll see something soon.
You are able to use a 3rd party email address as your Apple ID. It has been available for a while. I do have an iCloud email address, but a personal domain hosted on google, one that I use for everything. I have made that my AppleID too ;)
 
  • Like
Reactions: jhollington
You are able to use a 3rd party email address as your Apple ID. It has been available for a while. I do have an iCloud email address, but a personal domain hosted on google, one that I use for everything. I have made that my AppleID too ;)
I think you’re misunderstanding me. I know I can have third party emails, that’s why I wrote “update it as my primary email” because I already have @icloud.com, and @gmail.com.. once you create an @iCloud.com it will always be your Apple ID regardless if you add a @gmail.com. That’s why I said I would hate to have 3 emails for my Apple ID.
 
Don't think it'll result in subdomains... This would be too confusing for most people that have never seen subdomains for emails. Furthermore this would result in too many fake possibilities like:
steve.jobs@jobs.icloud.com
jobs@steve.icloud.com
steve@jobs.icloud.com
steve.jobs@icloud.com
(...)

I think this will result in a interface in cooperation with a DNS registry to have an one click solution (like outlook and GoDaddy).
Right? I would hope that I could settle with my custom Apple domain and the take off my @icloud.com from My Apple ID because it’s being stuck to my profile along with my @gmail.com, imagine have 3 when costumes domains come out… no thanks
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.