You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I have major problems using Exchange in Mountain Lion. Under Lion everything worked fine (Mail, Calendar, Contacts incl. global address list). Under ML only Calendar works, Mail and Contacts show connection errors. Our corporate server is Exchange 2007.
Has somebody a fully working Exchange in ML?
Any ideas?
Many thanks!
I've read all the workarounds on the thread. I don't have time to try everyone of these solutions. I use exchange in Mac Mail for university business and I have to shut down mail are restart it everytime I need to check my university account. School is starting soon and I'm constantly using the exchange account now.
Apple, hope you are listening. The dissapering email is a documented bug that is causing problems with your business users.
Denbee wrote:
I've read all the workarounds on the thread. I don't have time to try everyone of these solutions. I use exchange in Mac Mail for university business and I have to shut down mail are restart it everytime I need to check my university account. School is starting soon and I'm constantly using the exchange account now.
Apple, hope you are listening. The dissapering email is a documented bug that is causing problems with your business users.
Using a free servce for your business is not a good idea, get a real business email system.
Hello,
After upgrading to Mountain Lion:
Resolution
Mountain Lion includes full support for Autodiscovery. As part of this feature, each time Mail is opened, it asks your Exchange server what settings your mail account should use when connecting to the server.
If these settings differ from those that you have already added in Mail, they will be updated to reflect the latest settings from the server.
If you have trouble connecting to the Exchange server, contact your Exchange administrator or IT administrator.
Source : http://support.apple.com/kb/TS4363
Ah, great, they (Apple) are pointing their finger to Exchange now!
This is so stupid, all the information our Exchange servers supply using Autodiscovery is 100% correct. All serveraddresses for internal and external use are all true. But the way Mail under ML is handling this information is simply not the way it was under Snow Leopard and Lion. Both those OS-es had fine Exchange support. Until I upgraded to Mountain Lion.. 1 + 1 = 2 --> from my point of view, this is ML/Mail related, NOT Exchange related. The team that administers Exchange is accross the hall and nothing major has been changed the last few months. Furthermore: my MBP which is still running on Lion is working just fine with the exact same Exchange account.
This is just such a disappointment: first not acknowledging there's a problem, and when it's so obvious, blame the others... Cheap, very cheap.
(FWIW, I've also submitted this to Apple's feedback page)
This didn't work for me, perhaps Autodiscovery won't let me save any changes. There now seems to be an article from Apple on Exchange and Mountain Lion's Mail. The fingers have started pointing...
What a ridiculous point of view from Apple. Not very helpfull to satifies the users. Can not believe this is happening. I was so happy coming form Windows to finally own a range of Apple devices but this is not Apple at its best!!
However, changing the /etc/hosts file making the IP-adres of the external server the same as the name of the internal server seems to help a little bit.
Apple do something about this!!
Just added by Apple and sent to me by the tech senior who is working on solving my issues.
http://support.apple.com/kb/TS4363?viewlocale=en_US
Apple are being great in fixing this, with constant updates and calls to me. I have the same issues as everyone else. They tell me there is an update coming, and that issues will be resolved
Hold tight and keep the faith
Please try the procedure on a Windows machine to view your AutoDiscover settings:
Please let us know if you find the settings correct and Mountain Lion still does not work
Thank you for showing me that configuration tester. I have used an online service from Microsoft a few times (as suggested by our Exchange admins) and that turned out just fine (that was 3 weeks ago). Just now I tested the Autodiscover feature again using the method you suggested, and that also returns a correct configuration.
I'm comparing the server settings in Mail on my MBA (10.8) with the settings on my MBP (10.7). On my MBP the Exchange account works just fine, on my MBA it doesn't (just to be clear).
On the MBP I have changed the internal server address to the same as the external one, because that's what always reachable on any network: wired, wireless or thru the Internet. The internal server address is only reachable when you're connected to the wired network.
On the MBA, I can change the server addresses all I want, but after closing and opening Mail again, it's all back to what autodiscover tells it should be. Which sounds OK, but down the line, this doesn't work, no matter what network I'm on: wired, wireless or thru the Internet: just the problems as described.
Now comes the interesting part: how does Mail (or any other Exchange enabled client) know which server to use: the internal or external one? To circumvent that, I used the external server address on Lion, because that's always reachable. On Mountain Lion however: how am I supposed to know Mail enforces the use of Autodiscovery, even if I change it? Mail could warn me: "Are you sure you want override these settings?" But it doesn't. It could also make the server address fields grayed out, meaning I can see what the settings are, but cannot change them. That is called feedback in usability terms. And if Apple decided to always honour the Autodiscovery information, why make the server address fields viewable or editable in the first place? It's not clear what the intentions are and apparently it's still pretty legit from an Exchange point of view to have a configuration like the one we have. It's our choice to shut down a few ports on wireless for security reasons. That is why there is an internal and external address field. But why does Mail not honour it's user, (with a warning) if he explicitly makes a change?
Welp - after several calls with th Apple I received a call yesterday where the exective account administrator (begrudgingly) informed me that the engineers had sent a response stating that it was an issue with the informaiton provided by the exchange provider/host. Obviously everyone on this forum (and her) knows that this is not the case. Being a good boy I called my administrator and verified all the settings as correct, and then politely called her back and asked her to respond to the engineers that I had verified all settings with the administrator and that Exchange with Mac Mail worked under Lion, it does not work under Mountain Lion - the only thing that changed is the Operating System.
I was dissapointed that this was the response that she was actually instructed to give me, and I believe that she was as well. Apple has been very available and cooperative - the answer is Bush Leage to blame "the other guy" on the issue. It was a waste of my time, her time, and a cop out for the Engineers.
I am currently using Microsoft Outlook for Mac so my business is continuing. I HATE it. I am refusing to attempt any more of the Mac Mail workarounds because 1) they've proven to be temporary at best, and 2) Why should we? I want my computer to work as advertised without me becoming a software engineer.
As many others have said, I've learned my lesson regarding jumping on new software. There were bound to be bugs, I never suspected that there would be one this significant.
Good luck everyone. I'll let you know if/when I receive a follow up call from the Apple.
I've been following this thread closely over the past 24 hours, as I've just taken delivery of a new MacBook Pro with ML installed on it...
As everyone else has stated - I also have a 2011 MBP with Lion on it - no problem at all...
However, I have 2 colleagues with MBPs too. Both were running Lion and recently upgraded. One of them is still fine. The other guy was fine for a couple of weeks, but almost as soon as I mentioned this issue his laptop started having the same problem today!
Initially I was wondering if the issue was related to "upgrade" vs "fresh install" on ML - but seems thats nothing to do with it. All settings have been verified both between my ML & Lion MBPs as well as comparing my ML to my colleagues that are working fine. All seems to be the same - we're definitely on the same Exchange servers etc...
I spoke to AppleCare earlier - I know this is a bug, I was more interested in how I can downgrade my MBP to a fresh install of Lion for the time being until this is resolved, so at least I can carry on with it. Seems that THAT is not possible either - could possibly fudge it with a TimeMachine backup from my Lion machine, but not to install a fresh/vanilla Lion OS...
Certainly frustrating - and have a limited time on getting this resolved before it needs to be given to a new starter in the company - or else he's not going to have something to use when he starts working for us
Does anyone actually know if this is even going to be addressed in 10.8.1 - let alone a timescale on it? Read that its going to be seeded shortly - be interested if anyone on this thread has access to the Developer Forum to see if the issue is actually resolved there or not...
This may or may not be applicable to your situation, but nonetheless, I haven't seem the following conclusion suggested yet (ust admit I haven't read the entire discussion):
Based on the suggestion of subsriram, I checked and verified the autodiscover settings for my Exchange account. They are correct. I compared the server addresses (internal and external) and port numbers, SSL and path with my Exchange account on my MBP which is stil running Lion. I remembered I manually changed the internal server address to be the same address of the external one. In Lion this setting would remain saved, in Mountain Lion not, because it seems to strictly adhere to Autodiscover settings from the Exchange server. It simply will not let you change the server settings in Mail on ML.
This got me thinking about why I changed the internal server address on my Lion install: how can Mail determine when to use the internal and when to use the external server? Especially in my case, where we have a restricted wireless network compared to the wired network. So if the external would work anyway, why not use that address for the internal too? On Lion, Mail would remember my override. On ML it won't.
So the /etc/hosts workaround should do the trick in my case on ML. I edited the /etc/hosts file on ML to fake the OS (and thus Mail) to use the ip-address of the external server when referring to the internal server. After that, I re-opened Mail and got a certificate warning, which was to be expected because the name of the internal server is not included in the SSL-certificate of the external server. I explicitly trusted that certificate and rebooted my MBA (ML includes background processes for Calendar and Contacts too, that may not use this trick until a reboot). After the reboot, I haven't seen the empty Inbox or any empty mailbox anymore.
For me, this is a workaround that works, but it depends whether or not it will work for your Exchange setup in the same way. It's pretty easy to try in under 5 minutes, if you know you're way in Terminal.
... sigh... I just edited my previous post to report that my workaround does NOT work for me. While saving the update, Apple threw the maintenance note at me... Edit gone, also from browser cache. Thank you Apple...
The short version of my edit: I strongly believe it is not related to my specific Exchange set-up in combination with different networks, but it is an actual bug that should not have made it to the public.
Thanks D43m0ns for reporting back on this. My exchange server reports back the wrong servers and I was hoping if I get the administrator to fix it as outlined in the link, my Mountain Lion Mail will work again. Looks like it need not be the case from your experience. Disappointed to say the least! In any event, my IT Admin will fix the internal/external servers over this weekend and I will report back if that helps at all.
By the way I should add that the 'misconfigured' exchange server was working fine under Lion.
IMHO it still is a bug in Mountain Lion: I share the same thought: it all "just worked" on Snow Leopard and Lion. Both have "survived" the transition from SL to Lion and from Exchange 2007 to Exchange 2010 just fine. We're running Exchange 2010 since february this year, without issues (and we have 3000+ users on Exchange, so it's not likely that a misconfiguration will go unnoticed). Along comes the update to ML and voila, after several years being a happy and satisfied user on several OS X releases and Exchange versions: we all went a few steps backwards...
Apple claims to build professional product for professionals, by professionals. There's one too many "professional(s)" in this sentence. It's all a matter of perspective, but guess which one.
At least we can all agree upon that they are not handling the issues professionally, based on a recent article...
Exchange under Mountain Lion
