4 ms·
The problem has been explained very clearly in multiple comments, from different perspectives. You should try really really hard to not understand it at this po
by allarm 3y ago
The problem has been explained very clearly in multiple comments, from different perspectives. You should try really really hard to not understand it at this point.
- detourdog 3y agoI understand the issue now. I admit it took me longer than most people to understand. I hope you can admit that it is a very subtle issue. This is Apple babysitting their users. Apple needs to make sure that if their customer think that email is configured certain services are active. If an Apple customer has to make sure that each service is configured and it should be done by whatever email client the customer chooses. I disagree that the issue is severe. My assumption is that if one is setting up another email application the host operating system assuming they will provide the users of the alternative email client will also provide the mechanism for making it the default email client. That is not an unreasonable assumption for the host OS to make in my view. Email is a little different than browsers in at least 2 respects The biggest difference is that an established legal precedent that a host OS should provide a direct interface for selecting the default browser. The browser is also a single protocol application http:. The second is that an email client is multiple protocols. Do you want different default accounts depending if it's pop or imap? What about sending which accounts to do you to use and how. All of these options are in Mail.app and I have used many variations where default account might not cut it. I'm also willing to drop the whole thing because I bet at some point it won't be an issue if it is an issue.