Just can't believe this. I've tried everything. The whole reason I switched to a Mac was that the software worked and it was simple yet integrated. I've tried every tip I can locate. Nothing is working. So now I have to run Outlook in Parallels? Sheesh...
Oh and by the way, that didn't work either...
This is all on a mac that worked just fine prior to the installation of 10.8.2. The last exchange message I received was on 9/17.
I am also having issues with it! Exchanged worked on and off for a while in Mail after upgrading to Mountain Lion (it had always worked fine in Lion), but one day it decided to stop working entirely. I can still send/receive mail, but I can't see messages older than the last time Mail was launched. That means, if I close Mail, all my Exchange messages are gone. If I access the same account with Outlook for Mac, it works just fine, so it has to be an issue with Mail for Mountain Lion. Notes, Reminders, Contacts and Calendar work just fine, but those are the least important parts in my usage!
I think I have found somthing that works for us - I've edited three machines and they all seem to be working even better than before.
MB Air with 10.8.2 using Apple Mail to connect to two different Hosted Exchange Accounts (godaddy)
1 - Remove all Hosted Exchange Accounts (mail, contacts, calendars) using System Preferences>Mail, Contacts, Calendar.
2 - Add all Hosted Exchange Accounts using Preferences>Mail, Contacts, Calendar.
3 - Inside Mail Preferences I unchecked "Use Autodiscover Service"
4 - Inside Mail Preferences I copied the "External Server" name to the "Internal Server" name field so that they matched (since it is a hosted account at godaddy we always use the external server).
THIS SOLVED MY PROBLEM!!!!!!!!!
What if your hosted exchange provider works with several parallel servers (in my case six). Then this solution does not work, as you exactly need autodiscover service, as the hosted plattform decides for every requrst, via which server you have to get in (at least this is what I understood from the hotline of our provider). Thanks for feedback.
congratulations on having a terrible IT policy
first off if its broke then reboot to recovery and immediatly restore to a previous state from a time machine backup. this way you can't blame anybody for lost $$$ because you will be back up rather quickly and not have to talk trash on this forum due your lack of proper planning. Once a solution is found then you can update again.
any well ran IT department will not allow any random user to install updates, why? because you run a risk of not having things go through correctly. this is true for ANY computer
your employers IT should have something called a test environment where they have a non production Mac to test on. That way if an update doesn't succeed they can wait for a fix or figure out what needs to be done to resolve the issue BEFORE PEOPLE INSTALL UPDATES ON COMPUTERS THAT HELP MAKE MONEY.
I'm also having these problems. The saved autodiscover settings don't correspond with what's shown in the user interface. Sometimes I can edit the internal server even if autodiscover is checked. The Apple developers have really screwed up on this one. Not only does the GUI not work properly, but the actual synchronization on the back end is messed up. I typically have to wait 20-30 minutes in the mornings (after waking from sleep) before my first batch of email comes in. After that it's fine for the rest of the day. I don't have time to wait for 30 minutes before I can start replying to emails in the morning.
I've had most luck checking and unchecking autodiscover, checking and unchecking SSL, changing the internal servers and restarting Mac Mail several times. Mostly 5 minutes of messing around will get me to the point that it gets through. I can tell things are starting to work by looking at the activity window (cmd-alt-0).
Apple: please sort this out. Mac Mail and Exchange haven't been working together well for years, and this is simply embarrassing. People are flocking to Outlook. Do something about your platform!
You are right, for a company with an IT department. this is not the truth for hosted exchange solutions. There nobody is testing in a testlab before people install an update.
Besides, why isn't Apple testing their software in their test environment? This problem should already be solved before releasing this crap.
Well....ok...it looks like my Autodiscover turned itself back on.... but the internal and external server names are still the same (both were made to match the external server address).
However, SO FAR SO GOOD!! I'm on about day 3 and me and 4 other MBAirs are working better than ever before.
Try it and let us know how it works.
I am experiencing the same issue and I have found that changing the autodiscover settings so that the internal and external server settings are identical doesn't help. Nor did deleting the mail account and recreating it from scratch.
However what solved the problem for me is that if I connect a VPN from my macbook pro to the network where my Exchange server is hosted, thereby fooling my mac into thinking it is physically connected to the same LAN as the Exchange server, all of the intermittent connection problems are solved and mail works like it did under Snow Leopard. It is not neccessary to change any of the mail server settings to make this work - Just connect the VPN. Disconnect the VPN and the intermittent issues return.
I can only conclude that the bug is in the mechanism for connecting to the exchange database via the OWA gateway. As others have said, this method is rock solid under iOS so why wont it work reliably under OSX???
Apple - you must realise that these kinds of bugs waste masses of time for hundreds of thousands of users. I can't see how it was missed in the Beta release of 10.8.2
Important information to admins with on-premise Exchange 2010 servers, using Kemp Loadmaster 3600 setup as instructed in the Kemp guides:
OSX 10.6.x works without any problems connecting throug Kemp Loadmaster.
OSX 10.7.x and 10.8.x works only if you connect directly to the CAS servers.
After dumping some of the traffic we noticed that the new versions of iCal and Contacs has changed their requests to the CAS and that does not work if Kemp has been setup as mentioned in the docs. The reason could be that the new versions do not conform to standards or Kemp not recognizing the request correctly or inspecting the requests incorrectly.
What we did on the Kemp to fix it was:
Changed "Service Type" to "Generic" instead of "HTTP/HTTPS".
Changed "Server Initiating Protocols" to "Other Server Initiating" under the "Standard Options".
This way we tell Kemp to just make SSL offloading and sent the request to the CAS without inspecting and messing with the protocol.
Finally we can move our Mac mailboxes from 2007 to 2010...
Message was edited by: BrianNicolaisen